context safety score
A score of 37/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
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
JavaScript intercepts all movie title link clicks (.mh-loop-title) and forces window.open() to 'https://kidsinstancesfavor.com/npw80ak2?key=4e29afc51f124f171ea0d5771e57df88' in a new tab, ignoring the legitimate href. This silently redirects users away from expected content to an unrelated third-party URL with a tracking key, consistent with malvertising or traffic redirection schemes. (location: page.html:919-926 (div#net9j-3844360512); also visible in page-text.txt:466-473)
brand impersonation
The site operates as 'Net9ja' (net9ja.com.ng) and aggressively targets the brand identity of 'NetNaija' (a well-known Nigerian movie download site) throughout its metadata, SEO tags, and page titles. Meta description and OG tags repeatedly use 'netnaija', 'NetNaija.com', 'NetNaija Movies' to capture search traffic intended for the legitimate NetNaija brand. (location: page.html:11-23 (meta description, og:description, twitter:description))
hidden content
A fixed-position overlay div (#net9j-22331536) is injected at the bottom of the page with z-index:100 and position:fixed, containing ad code. The close button has no visible label (empty span). This pattern is used to display intrusive or hidden ads that overlay page content without clear user consent. (location: page.html:899-916 (div#net9j-22331536, .wpInsertTemplateTag with position:fixed, z-index:100))
malicious redirect
Multiple ad zones load scripts dynamically from 'adsbetnet.com' using an obfuscated self-executing function pattern with fallback domain arrays. The domain 'adsbetnet.com' is not a recognized major ad network and is consistent with rogue ad networks known to serve malvertising, forced redirects, or popunders. (location: page.html:449-471, 554-564, 929-938 (zones 909012822, 987285430, 994834272, 983432504))
obfuscated code
Ad loader scripts use an obfuscated IIFE pattern with single-letter variable names (w,d,o,g,r,a,m), dynamic script injection via document.createElement, and a domain fallback chain array (['adsbetnet.com']). The pattern obscures the true ad network identity and allows runtime switching of script sources, a common technique in malvertising chains. (location: page.html:450-458, 462-470, 555-563, 930-937)
curl https://api.brin.sh/domain/net9ja.com.ngCommon questions teams ask before deciding whether to use this domain in agent workflows.
net9ja.com.ng currently scores 37/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.