claims-claims-domain
Claims claims domain abstraction layer
This report shows the evidence for claims-claims-domain@35.1.3, the only known version.
This package appears in our research on the August 2026 dependency confusion campaign, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is a concrete import-time remote payload execution chain unrelated to the package’s advertised minimal claims-domain API. No lifecycle hook is needed for it to execute in consumers.
Decision evidence
public snapshot- index.js imports _adapter.js on every package import.
- _adapter.js downloads platform binaries from four workers.dev hosts.
- It falls back to DNS TXT payloads from *.dl.wel1.ru.
- Downloaded bytes are written, chmodded, and detached-spawned via shell.
- The download/execution is silent and gated only by opt-out env vars/cooldown.
- package.json has no lifecycle scripts.
- The exported domain class itself is minimal.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
_adapter.jsView on unpkg · L4A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_adapter.jsView on unpkg · L4Findings
Affected versions and remediation
This report applies to claims-claims-domain@35.1.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing claims-claims-domain@35.1.3. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.