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
malicious redirect
The page at popcorn-tracker.org contains no visible content but immediately loads a zero-pixel tracking beacon from 'l.cdn-fileserver.com/bping.php' and dynamically injects an iframe pointing to 'searchresultsworld.com'. This is a parked/hijacked domain acting as a redirect intermediary — the entire page is a silent redirect mechanism with no legitimate content. (location: page.html: <img> beacon (0px hidden) and <script> iframe injection targeting https://searchresultsworld.com/sr/754870121/SAFEFRAME.html)
hidden content
A 0x0 pixel image beacon is embedded with 'display: none !important' styling. It silently exfiltrates visitor metadata including IP (wsip=170762594), ASN, session ID (hvsid), country code (cc=US), and the originating URL to l.cdn-fileserver.com/bping.php. This is covert data collection with no user visibility or consent. (location: page.html: <img> tag with width='0px' height='0px' style='display: none !important')
obfuscated code
The page's sole JavaScript block uses a custom substitution cipher (Caesar-style shift cipher using the key string 'cut2FAC698y RjrwgLUqsSo71/J53V~4lPWe-0_nfBXaKTbizdvkZ|DpGMNIYHxO=QhEm' with shift value 11) to encode parameters before appending them to the iframe src URL. The function 'm()' encodes data passed to the ad network, deliberately obscuring what data is being transmitted. Additionally, all URL parameters are heavily percent-encoded to evade inspection. (location: page.html: <script> block, function m(e) with ek/es cipher, and encoded l2u/l2h/so URL parameters)
hidden content
The script creates a div with class names 'adclass googleAdSense MediumRectangleAdPanel adv_left browse-banner_ad sponsored' and id 'abp_px' styled with 'opacity: 0; visibility: hidden; width: 0; height: 0; position: absolute; top: -9999px; left: -9999px' — this is an ad-blocker detection probe. If an ad blocker is detected, it fires additional tracking beacons to both 'l.cdn-fileserver.com/log' and 'popcorn-tracker.org/sk-lgprxfwd.php', flagging the visitor's ad-blocker status. (location: page.html: <script> block, adblock detection div with id='abp_px' and alc beacon array)
malicious redirect
The domain popcorn-tracker.org hosts a script endpoint 'sk-lgprxfwd.php' (likely 'skip-log-proxy-forward') that is called as a logging/tracking beacon when ad-block is detected. The naming pattern and usage suggest a server-side redirect/forwarding proxy endpoint, consistent with traffic monetization or redirect chain infrastructure. (location: page.html: <script> m.alc array entry {ht:'https://popcorn-tracker.org', pt:'sk-lgprxfwd.php', tp:'DM'})
curl https://api.brin.sh/domain/popcorn-tracker.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
popcorn-tracker.org 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.