context safety score
A score of 42/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
js obfuscation
JavaScript uses Function constructor for runtime code generation
prompt injection
Hidden HTML element contains AI-targeting instructions
hidden content
A hidden anchor tag with `style='display: none'` and `aria-hidden='true'` links to an AWS API Gateway endpoint: https://v0gikxeped.execute-api.us-east-1.amazonaws.com/prod/ with rel='nofollow'. This invisible link points to an unbranded, opaque external endpoint and is not visible to users, suggesting potential use for tracking, exfiltration, or covert redirection. (location: page.html:65)
malicious redirect
The hidden link targets an AWS Lambda/API Gateway URL (https://v0gikxeped.execute-api.us-east-1.amazonaws.com/prod/) that is completely opaque and unrelated to the plu.mx or Elsevier domain. Combined with its hidden nature, this could serve as a covert redirect or data exfiltration endpoint. (location: page.html:65)
credential harvesting
The page presents a sign-in form with username and password fields (POST to /sign_in) while simultaneously displaying a 'sunset' banner stating the dashboard is no longer available. An active login form on a deprecated/sunset service is anomalous and raises concern that credentials submitted may not be processed legitimately or may be harvested without proper backend handling. (location: page.html:130-173, page.html:179-182)
social engineering
The sunset banner prompts users to switch to a new email address 'PlumXsupport@elsevier.com', while the existing support contact in the sign-in form still references 'support@plumanalytics.com'. This conflicting contact information could cause user confusion and direct sensitive support inquiries to unverified channels. (location: page.html:169-171, page.html:180)
curl https://api.brin.sh/domain/plu.mxCommon questions teams ask before deciding whether to use this domain in agent workflows.
plu.mx currently scores 42/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.