context safety score
A score of 45/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 contains heavy hex-escape encoding typical of obfuscation
obfuscated code
The page contains heavily obfuscated JavaScript using hex-encoded string literals (_0xebe8=["\x34\x62\x63..."]), base64-encoded data decoded via atob(), and AES decryption (slowAES.decrypt) to compute a cookie value at runtime. This pattern is characteristic of bot-detection bypass mechanisms or fingerprinting scripts that conceal their true behavior from static analysis. (location: page.html:4-5)
malicious redirect
After decrypting and setting a cookie, the script unconditionally redirects the browser via location.href to https://apkmodjoy.net:443/. The redirect destination is determined by opaque, encrypted runtime logic, making it impossible to verify the final destination statically. This gating pattern is commonly used to serve different content to bots vs. real users, or to chain redirects to malicious payloads. (location: page.html:5)
hidden content
The visible page content is entirely blocked behind a JavaScript wall — users without JS see only a red warning message, while the actual page content is loaded dynamically after cookie-setting and redirect logic executes. This deliberately hides the true page content from crawlers, security scanners, and AI agents, a technique used to evade detection. (location: page.html:3, page-text.txt:2)
hidden content
A cookie named 'VO269wPABA-cL' is set to the AES-decrypted value of an encrypted ciphertext, using a key derived from obfuscated hex and base64 values. This covert session token is set before any visible content loads, potentially used for tracking, fingerprinting, or gating access to malicious content for targeted visitors. (location: page.html:5)
curl https://api.brin.sh/domain/apkmodjoy.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
apkmodjoy.net currently scores 45/100 with a suspicious verdict and medium 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.