context safety score
A score of 40/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
cloaking
Page checks user-agent for bot/crawler strings to serve different content
cloaking
Page conditionally redirects based on referrer or user-agent
js obfuscation
JavaScript uses Function constructor for runtime code generation
hidden content
Browser fingerprinting script using FingerprintJS (loaded from cdn.jsdelivr.net) collects extensive device data including visitorId, canvas fingerprint, screen dimensions, pixel ratio, color depth, browser user agent, and page URL, then POSTs to https://r.cdnpure.com/report?project=web3_navigator. This operates silently on a 1% sampling rate with no user disclosure. (location: page.html:1226-1427, page-text.txt:907-1108)
hidden content
WebRTC RTCPeerConnection is used to leak both local (LAN) and public IP addresses via ICE candidate harvesting, hashing them with DJB2 and including them in the fingerprint report sent to r.cdnpure.com. This bypasses VPN/proxy protections to obtain the user's real local network IP. (location: page.html:1369-1426, page-text.txt:1050-1107)
hidden content
JA3/JA4 TLS fingerprinting: script fetches https://ja34.apppure.net/api/web to obtain the browser's TLS fingerprint (ja3+ja4 hashes), then reports them along with navigator.webdriver status, host, and full URL to r.cdnpure.com. The webdriver detection flag is explicitly captured, indicating bot/agent detection capability. (location: page.html:1197-1223, page-text.txt:878-904)
hidden content
Interaction surveillance script captures click coordinates, target element tag/ID/class, mousemove positions, keydown keycodes/key values, and scroll offsets, then POSTs to https://r.cdnpure.com/report?project=web_navigator. Keydown capture includes actual key values which could log typed characters. (location: page.html:1429-1516, page-text.txt:1111-1196)
hidden content
Base64-obfuscated domain blacklist in apkpurePartnerConfig: ["YXBrcHVyZS5jb20=", "bS5hcGtwdXJlLmNvbQ==", ...] decodes to apkpure.com, m.apkpure.com, and regional variants. The partner injection logic (SnapTube link) is suppressed on these domains but enabled elsewhere, enabling covert partner link injection on non-blacklisted domains without visible source-level domain names. (location: page.html:1521-1528, page-text.txt:1203-1208)
malicious redirect
JavaScript redirect logic targets mobile user agents (Android, iPhone, iPad, etc.) redirecting to https://m.apkpure.com/ by decoding a URL-encoded string and calling location.href. Cookie-controlled with 'mobile' cookie check; stores referrer and timestamp in window.name before redirect, which persists across navigation and could be read by the destination page. (location: page.html:46-83)
hidden content
Firebase push notification token (FCM) is silently uploaded to https://tapi.pureapk.com/v3/report_token including device ID (qimei), user ID, timezone offset, and domain when browser notification permission is already granted. Token upload occurs without a new permission prompt, leveraging pre-existing permission. (location: page.html:1100-1146)
curl https://api.brin.sh/domain/apkpure.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
apkpure.com currently scores 40/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.