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
prompt injection
Hidden HTML element contains AI-targeting instructions
malicious redirect
Third-party script loaded from 'udzpel.com' with a base64-encoded payload in the filename ('waWQiOjExOTI4MzMsInNpZCI6MTQwNDcxNCwid2lkIjo2ODIxODUsInNyYyI6Mn0=eyJ.js'). This domain is an known ad/traffic redirector associated with aggressive pop-under and redirect ad networks that frequently deliver malvertising payloads. (location: page.html:141 — <script async src="https://udzpel.com/pw/waWQiOjEx...">)
malicious redirect
Third-party script loaded from '21104.impseeineclots.com' — a subdomain pattern consistent with adware/malvertising networks that serve forced redirects, pop-ups, and potentially exploit kits to end users. (location: page.html:144 — <script src="https://21104.impseeineclots.com/4/js/272715" async>)
hidden content
Commented-out script tag referencing 'diagramjawlineunhappy.com/t/9/fret/meow4/2038849/d913a84d.js' — a obfuscated third-party domain consistent with ad-network or malware distribution infrastructure. The comment suggests this script was previously active and may be re-enabled, or the domain is being rotated. (location: page.html:143 — <!--<script src="//diagramjawlineunhappy.com/t/9/fret/meow4/2038849/d913a84d.js"></script>-->)
obfuscated code
All script tags use the non-standard MIME type 'b7fb0b3967238569c2995fe7-text/javascript' instead of 'text/javascript'. This is a Cloudflare Rocket Loader technique, but it also effectively hides script execution intent from basic scanners and delays parsing — a pattern sometimes abused to obscure malicious script loading from security tools. (location: page.html:122–144, 1837–1868 — type="b7fb0b3967238569c2995fe7-text/javascript" on all script tags)
social engineering
The site hosts and distributes what it explicitly labels as 'Celebrity Leaks', 'Leaked Sextapes', and non-consensual intimate imagery (NCII) of named individuals (e.g., 'Rivers Kenpoly Babe Mimi Nude', 'Michou Mbembele Leaked Video Call', 'UPSA Student Leaked Sextape'). This constitutes social engineering of visitors into viewing and sharing non-consensually distributed content, and lures users with real names to drive engagement and repeat visits. (location: page.html:700–1784 — post listing grid; page-text.txt:215,331,389,911)
hidden content
The CSS rule '.screen-reader-text { display: none; }' hides screen-reader text from all users rather than only visually hiding it accessibly. While this is a minor CSS practice issue, combined with the ad network scripts, it may be used to suppress visible indicators of injected content from human review. (location: page.html:150–152 — <style id="wp-custom-css">)
curl https://api.brin.sh/domain/naijafap.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
naijafap.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.