context safety score
A score of 33/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
obfuscated code
Two identical large obfuscated JavaScript blocks appear in the page (in both the header area and body). Each uses a URL-encoded string with a Caesar-cipher-style positional character rotation (charCode offset by index mod 95) to hide the actual payload. The script loads ad network code (clickadu.net) and likely fingerprinting/tracking logic. The obfuscation pattern is characteristic of malvertising loaders that dynamically construct URLs and redirect targets at runtime, making static analysis impossible without execution. (location: page.html:452-453 and page.html:907-908)
malicious redirect
Multiple navigation links and the promotional banner redirect users through the third-party tracker domain 'tt.culinar9sync.com', an affiliate/redirect chain domain unrelated to the site's stated content. Links labeled 'AI PORN', 'AI Jerk Off', and 'Premium' all resolve through this tracker. The promotional banner ('AI Porn is here, Create and Fap') also triggers window.open() to the same tracker URL (https://tt.culinar9sync.com/685c07c5ddb784ecaf8c168b) on both title and button click, without disclosing the final destination to the user. (location: page.html:387-393, 614, 636, 658)
social engineering
An intrusive promotional banner overlays the page on load with sexually explicit language ('AI Porn is here, Create and Fap', 'Try Free 🔞') designed to compel user clicks, which open a new window to an opaque affiliate tracker URL. The banner uses urgency and provocative content to bypass user caution and drive clicks to an unverified third-party destination. (location: page.html:370-394)
obfuscated code
External script loaded from 'https://turbostats.xyz/blackhole.js' followed by instantiation of a 'Blackhole' object with a hardcoded API key ('WnGtc9Ubxccy73Wz') posting to 'https://turbostats.xyz/pAPI'. The domain name ('turbostats', 'blackhole') and usage pattern suggest a covert analytics/tracking beacon. The purpose and data collected are not disclosed to users. (location: page.html:8-9)
hidden content
A favicon and logo asset are loaded from an external domain 'simpcity.rs' (different from the current domain 'simpcity.is'), and avatar images are served from 'http://simp6.selti-delivery.ru' over plain HTTP. Loading assets from .ru domains via HTTP introduces risk of asset substitution or tracking pixel injection without user awareness. (location: page.html:11, 1099)
malicious redirect
A third-party ad script is loaded asynchronously from '//adv.clickadu.net/on.js' and '//adv1.clickadu.net/bn.js' with inline callback functions (wrkuwxv, rbefro). Clickadu is a known adult ad network associated with aggressive redirect ads and pop-unders. Combined with the obfuscated loader scripts, these could trigger forced redirects or malvertising payloads on page load or user interaction. (location: page.html:453, 908)
obfuscated code
An external SDK script is loaded from 'https://jpg6.su/sdk/pup-sc.js?7' with data attributes pointing to 'https://jpg6.su/upload'. The jpg6.su domain is a third-party image hosting service embedded as a script SDK, injecting upload functionality into the forum's post editor via DOM manipulation (data-sibling selectors). This could be used to intercept user-uploaded content or inject malicious UI elements. (location: page.html:4)
curl https://api.brin.sh/domain/simpcity.isCommon questions teams ask before deciding whether to use this domain in agent workflows.
simpcity.is currently scores 33/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.