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
brand impersonation
Site distributes modified ("modded") versions of major commercial apps and games including YouTube Premium, Netflix, CapCut, YouTube Music, FaceApp Pro, X (Twitter), Nova Launcher Prime, and others, using their official brand names, logos, and promotional imagery to attract users to unauthorized cracked APKs. This constitutes systematic brand impersonation of Google, Netflix, ByteDance, Meta, and dozens of other rights holders. (location: page.html: hero carousel (lines 430-540), featured section (lines 571-841), updated apps/games sections throughout)
social engineering
The site uses persuasive UI patterns to normalize illegal software distribution: 'MOD' badges rendered in official-looking red pill labels, 'Updated' green badges implying legitimacy, star ratings, file sizes, and version numbers mimicking legitimate app stores (Google Play). The 'GET' and 'Download' CTAs use urgency framing identical to official distribution platforms, deceiving users into trusting the source. (location: page.html: all app/game listing cards throughout the page, e.g. lines 448-453, 610-612)
social engineering
Footer copyright reads '© 2026 GETMODAPK.COM' while the domain is getmodsapk.com — a deliberate variation that creates confusion between two similarly named piracy sites and obscures the true operator identity. This inconsistency is a trust-manipulation technique. (location: page.html:3630, page-text.txt:3340)
brand impersonation
The site lists 'NETFLIX' as a standalone footer navigation link pointing to a Netflix modded APK page (https://getmodsapk.com/9458-netflix-modded-apk/), and features 'Red Dead Redemption NETFLIX' as a game listing, co-opting the Netflix brand to lend credibility to unauthorized content distribution. (location: page.html:3657, page.html:751-795)
social engineering
The site prominently features NSFW-categorized content ('Lusty Buccaneers', 'Passion Industry', 'Action Taimanin') alongside mainstream content without age verification, using the same trusted app-store visual design to normalize adult content delivery via sideloaded APKs. This lowers user guard against potentially harmful downloads. (location: page-text.txt:1916-1943 (Lusty Buccaneers, Nsfw category), page-text.txt:2016-2043 (Passion Industry))
hidden content
Multiple carousel slide heading elements contain only a literal period ('.') as their h3 text (e.g., '<h3 ...>.</h3>') while the visible label is placed in a separate paragraph. This separates the SEO/crawlable title from the visual title, a technique used to serve different content to bots vs. users. (location: page.html:445, 473, 501, 529)
curl https://api.brin.sh/domain/getmodsapk.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
getmodsapk.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.