context safety score
A score of 48/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
cloaking
Page conditionally redirects based on referrer or user-agent
obfuscated code
Heavily obfuscated JavaScript block using a custom string-rotation decoder (resizetmotor_0xa2b81d / resizetmotor_0x2fb1 / resizetmotor_0x2bc3) with hex-encoded string arrays and self-shuffling logic. When decoded, the script fires on window.onload, reads window.location.hostname, constructs an img tag with display:none pointing to https://logo.page-source.com/resizeimage.ashx with the hostname embedded as a parameter, and injects it into document.body. This is a covert beacon/tracking pixel injected via obfuscated code that exfiltrates the visitor's hostname to a third-party domain not affiliated with Tata Motors. (location: page.html:line 83 — inline <script> block in <head>)
hidden content
A zero-dimension tracking pixel (width='0' height='0', display:none) is dynamically constructed and injected into document.body by the obfuscated script. The pixel calls https://logo.page-source.com/resizeimage.ashx?ig=<hostname>&sz=282401 — an external, non-Tata domain — silently beaconing the page hostname on every page load without any user awareness or consent disclosure. (location: page.html:line 83 — decoded payload of obfuscated onload handler, injected into document.body)
malicious redirect
The link 'https://www.globalservices.tatamotors/' (missing TLD — not a valid URL) is used as a 'Visit Website' href for 'Tata Motors Global Services Ltd.' This malformed URL could resolve unexpectedly in some browsers or be used for typosquatting/redirect abuse, and does not match the expected domain pattern (tatamotors.com). (location: page.html:line 453 — <a href="https://www.globalservices.tatamotors/">)
curl https://api.brin.sh/domain/tatamotors.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
tatamotors.com currently scores 48/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.