context safety score
A score of 41/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
js obfuscation
JavaScript appears to use a common packer pattern (p,a,c,k,e,d)
prompt injection
Hidden HTML element contains AI-targeting instructions
malicious redirect
Third-party script loaded from 'udzpel.com' with a base64-encoded filename ('waWQiOjExOTI4MzMsInNpZCI6MTQwNDcxNywid2lkIjo2ODIxOTIsInNyYyI6Mn0=eyJ.js'). This domain is unrelated to the site and the obfuscated filename is a common pattern used by ad-fraud and malvertising networks to deliver drive-by redirects or malicious payloads. (location: page.html:226)
malicious redirect
Third-party script loaded synchronously from 'diagramjawlineunhappy.com' — a randomly-generated-looking domain with no obvious legitimate purpose, a hallmark of malvertising/redirect network infrastructure. The 'data-cfasync=false' attribute bypasses Cloudflare rocket-loader, ensuring the script executes unconditionally. (location: page.html:228)
obfuscated code
Commented-out block contains a packed/obfuscated eval() call using the p,a,c,k,e,d packer pattern. While commented out, its presence indicates the site has hosted or tested anti-debugging/obfuscated code. The script detects devtools and replaces the entire page HTML with an error message, a technique used to obstruct security researchers and automated scanners. (location: page.html:1582-1593)
hidden content
All first-party scripts (jQuery, Google Tag Manager, theme JS, plugin JS) have their type attribute set to a custom MIME type 'fc0c5859d6d1613f9e1833dc-text/javascript' instead of 'text/javascript'. This non-standard type prevents browsers from executing scripts natively and requires Cloudflare Rocket Loader to re-enable them. While this is a known Cloudflare mechanism, it effectively masks script execution from static scanners and defers all JS to a single Cloudflare-controlled loader. (location: page.html:108,217-218,1566,1570-1581)
social engineering
Site hosts and prominently features 'Celebrity Leak' and 'Leak Videos' categories prominently promoting non-consensual intimate imagery (NCII) of named real individuals (e.g., YesJulz, Barakat Olawumiwealth, Michou Mbembele, Shannel). This constitutes a social engineering lure targeting users with promises of stolen private content, commonly used as a vector to deliver adware, malvertising, or credential-harvesting overlays. (location: page.html:246,584-593,1128-1137)
hidden content
A hidden 1x1 invisible iframe is injected into the document body by an inline Cloudflare challenge script. The iframe has style='position:absolute;top:0;left:0;border:none;visibility:hidden' and is used to inject and execute additional scripts via 'cdn-cgi/challenge-platform/scripts/jsd/main.js'. While standard Cloudflare bot-detection, the hidden iframe pattern warrants flagging as it can be repurposed for clickjacking or hidden script execution. (location: page.html:1595)
curl https://api.brin.sh/domain/naijared.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
naijared.com currently scores 41/100 with a suspicious verdict and low confidence. The goal is to protect agents from high-risk context before they act on it. Treat this as a decision signal: higher scores suggest lower observed risk, while lower scores mean you should add review or block this domain.
Use the score as a policy threshold: 80–100 is safe, 50–79 is caution, 20–49 is suspicious, and 0–19 is dangerous. Teams often auto-allow safe, require human review for caution/suspicious, and block dangerous.
brin evaluates four dimensions: identity (source trust), behavior (runtime patterns), content (malicious instructions), and graph (relationship risk). Analysis runs in tiers: static signals, deterministic pattern checks, then AI semantic analysis when needed.
Identity checks source trust, behavior checks unusual runtime patterns, content checks for malicious instructions, and graph checks risky relationships to other entities. Looking at sub-scores helps you understand why an entity passed or failed.
brin performs risk assessments on external context before it reaches an AI agent. It scores that context for threats like prompt injection, hijacking, credential harvesting, and supply chain attacks, so teams can decide whether to block, review, or proceed safely.
No. A safe verdict means no significant risk signals were detected in this scan. It is not a formal guarantee; assessments are automated and point-in-time, so combine scores with your own controls and periodic re-checks.
Re-check before high-impact actions such as installs, upgrades, connecting MCP servers, executing remote code, or granting secrets. Use the API in CI or runtime gates so decisions are based on the latest scan.
Learn more in threat detection docs, how scoring works, and the API overview.
Assessments are automated and may contain errors. Findings are risk indicators, not confirmed threats. This is a point-in-time assessment; security posture can change.
integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.