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
script/meta redirect patterns detected in page source
social engineering
The site distributes modified (cracked/modded) APKs of paid and premium apps including Spotify, YouTube, Disney Plus, Telegram, WhatsApp, CapCut, and many others with labels like 'Premium Unlocked', 'Unlock VIP', and 'Unlimited Money'. This constitutes deceptive distribution of pirated software, encouraging users to bypass legitimate purchase flows and potentially exposing them to trojanized binaries. (location: page.html, page-text.txt — throughout game/app listings)
social engineering
An installation guide dialog explicitly instructs users to bypass Android's Google Play Protect security warning by clicking 'More details' then 'Install anyway', actively coaching users to disable a protective mechanism in order to sideload potentially untrusted APKs. (location: page-text.txt lines 4402-4416; page.html installation guide dialog)
malicious redirect
Third-party ad/tracking script loaded from suspicious domain 'jl.ankolisiloam.com' (zone ID 59500) via dynamically injected script tag. This domain is unrecognized and not affiliated with any major ad network, consistent with malvertising or traffic redirect infrastructure. (location: page.html line 1242: <script src='//jl.ankolisiloam.com/gSeEjd220r2k8LNcZ/59500'>)
malicious redirect
Push notification SDK loaded from 'push-sdk.com' with zone ID 1104473, tracking click_id and source_id URL parameters. Push notification abuse is a common vector for redirecting users to malicious pages or delivering adware-style persistent notifications. (location: page.html lines 212-232: push-sdk.com/f/sdk.js?z=1104473)
malicious redirect
DNS prefetch and preconnect established to 'zr.changarreviver.com' and 'valvalnumbest.com' — both are unrecognized third-party domains not associated with any known CDN or analytics provider, indicative of covert tracking or redirect infrastructure. (location: page.html lines 181-187: link rel=dns-prefetch/preconnect to zr.changarreviver.com and valvalnumbest.com)
brand impersonation
All static assets (CSS, JS, images, favicons) are served from 'cfgz1-resource.niceapkdown.shop' rather than playmods.net's own CDN. The domain 'niceapkdown.shop' is a third-party .shop TLD domain controlling all visual branding of the site, meaning a compromise of this domain would allow complete visual impersonation of PlayMods and replacement of all downloadable APK files. (location: page.html lines 190-205, 234, 344, 196 — all resource URLs)
brand impersonation
The site distributes modified APKs of well-known branded apps (Roblox, Minecraft, WhatsApp, YouTube, Spotify, TikTok, Instagram, Disney Plus, Grand Theft Auto) under the PlayMods brand without authorization from original developers, constituting brand impersonation of those original software publishers. (location: page.html and page-text.txt — app listings throughout)
hidden content
The page-hidden.txt file contains navigation menu items (game categories, language selectors, app categories) that are rendered with display:none in the DOM. While these appear to be legitimate hidden UI elements (dropdowns revealed on hover), they inflate the page's text content with hidden navigational text not visible to regular users. (location: page-hidden.txt; page.html header-layer divs with style='display: none')
social engineering
The site displays a prominent banner stating 'PlayMods.net is the only official website of PlayMods App. Please do not visit other fake url' — this is a trust-building social engineering tactic used to establish false legitimacy and discourage users from verifying the site's authenticity through other channels. (location: page.html lines 1262-1270; page-text.txt lines 916-918)
prompt injection
The page-hidden.txt contains raw JavaScript code blocks (Yandex RTB render calls, share functions) rendered as visible text within hidden elements. While not a direct AI prompt injection, these code fragments embedded in text extraction outputs could confuse automated AI analysis pipelines that process this page's text content. (location: page-text.txt lines 814-819, 901-906, 2957-2962; page-hidden.txt lines containing JS code)
curl https://api.brin.sh/domain/playmods.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
playmods.net 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.