context safety score
A score of 47/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
A stylesheet is loaded from 'https://www.restomp-excity.online/assets/style.min.css?query=1766419322' — an unknown third-party domain ('restomp-excity.online') with no apparent relationship to JetPunk. This domain does not match any known CDN or ad partner and could serve malicious CSS capable of UI redressing, click-jacking, credential harvesting overlays, or content injection. (location: page.html:37 — <link rel="stylesheet" href="https://www.restomp-excity.online/assets/style.min.css?query=1766419322" />)
obfuscated code
A large block of heavily obfuscated JavaScript is present using array-based string obfuscation, encoded variable names, and runtime string reconstruction (WP/dKxLs, WRJcQSkKWOG, etc.). This pattern is characteristic of malware loaders, skimmers, and credential-harvesting scripts that evade static analysis. The obfuscated block is inline and executes immediately via an IIFE. (location: page.html:36 — <script data-cfasync="false">(function(){function m(){const I=[...obfuscated array...])
hidden content
Multiple script tags use a non-standard 'type' attribute value ('7b3d6b8cd337f6a6faef3d28-text/javascript' and '7b3d6b8cd337f6a6faef3d28-application/javascript') which prevents browsers from executing them natively. This is a Cloudflare Rocket Loader technique, but the same token is applied to ALL scripts including the obfuscated inline block and the external third-party script from 'scripts.webcontentassessor.com', meaning a custom loader controls when and how these scripts execute — obscuring execution flow from scanners. (location: page.html:34-35, 950, 956-959, 963-964 — type='7b3d6b8cd337f6a6faef3d28-text/javascript')
malicious redirect
A script is loaded from 'https://scripts.webcontentassessor.com/scripts/a6723e705684aad5e2a47bb1623356a36bd78e7b42100c0895c7532da150e803' — an external domain not affiliated with JetPunk. 'webcontentassessor.com' is an ad-tech/content classification service whose scripts have been associated with aggressive tracking and potentially unwanted behavior. The script is loaded with a hash-like path, making the content opaque. (location: page.html:35 — <script type="..." src="https://scripts.webcontentassessor.com/scripts/a6723e705684...">)
curl https://api.brin.sh/domain/jetpunk.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
jetpunk.com currently scores 47/100 with a suspicious verdict and medium 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.