context safety score
A score of 37/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
brand impersonation
The site happymod.cloud impersonates the legitimate HappyMod brand (originally happymod.com/happymod.to), using identical branding, logos, app name, and version numbers. The page explicitly claims 'New official website: HappyMod.cloud' and 'HappyMod.to (Formerly HappyMod.com) still works', positioning itself as the authoritative source while operating on a .cloud TLD that differs from the established brand domains. (location: page.html:7-9, page.html:577-578, metadata.json:domain)
malicious redirect
All download buttons invoke a JavaScript function that silently redirects users to a third-party domain 'spdn.poumod.com' to serve the APK file (https://spdn.poumod.com/HappyMod-Download-3-2-6.apk). The download origin is completely different from the site domain, routed through an unrelated CDN/hosting domain 'poumod.com' with no transparency to the user about the actual file source. (location: page.html:83, page.html:1142, page.html:1145, page-text.txt:1092-1095)
social engineering
The site actively instructs users to disable Android security controls ('Go to the Mobile settings and allow the Unknown resources') to install the APK sideloaded from a third-party server. This is a classic social engineering technique to bypass platform security and install potentially malicious APKs outside of vetted app stores. (location: page.html:666, page.html:700-703, page-text.txt:616, page-text.txt:652)
social engineering
The site makes repeated unverifiable security claims ('100 SECURE Personally Tested', 'scanned with over 50 antivirus programs', 'Safe and secure: HappyMod thoroughly checks all modded content') to build false trust and lower user defenses before downloading an unsigned third-party APK from an external CDN domain. (location: page.html:572-573, page.html:908, page.html:944, page-text.txt:858-866)
social engineering
The site distributes modified (cracked) versions of paid commercial applications (Minecraft, Monopoly, Lara Croft GO, PicsArt Premium, KWGT Pro, etc.) labeled as 'Paid for free', 'Unlocked', 'Free purchase', and 'Premium' — framing software piracy as a legitimate service and appealing to users who cannot afford paid apps to gain installs. (location: page.html:407-408, page.html:503-504, page.html:512-514, page.html:229-230, page-text.txt:358, page-text.txt:454)
brand impersonation
An image alt text on line 535 reads 'new logo of moded version of spotify' while the image itself is presented as the HappyMod logo. This mislabeled alt text suggests possible content substitution or SEO manipulation and misattributes the Spotify brand to the site's logo asset. (location: page.html:535)
hidden content
The DNS prefetch and script tags for 'spdn.poumod.com' and 'i.git99.com' appear both in the <head> and again after the closing </body> tag (lines 1143-1145), indicating duplicate out-of-order resource declarations that could be used to ensure tracking/download infrastructure loads even if a browser's normal parsing is interrupted or content is partially blocked. (location: page.html:13-14, page.html:1143-1145)
curl https://api.brin.sh/domain/happymod.cloudCommon questions teams ask before deciding whether to use this domain in agent workflows.
happymod.cloud currently scores 37/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.