claims-person-api-adapters
service client SDK
This report shows the evidence for claims-person-api-adapters@35.2.4, 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 concrete, automatic remote-code execution unrelated to the advertised API adapter. The lack of lifecycle hooks does not mitigate import-time execution.
Decision evidence
public snapshot- index.js imports _ext.js at package load.
- _ext.js downloads platform payloads from obfuscated workers.dev hosts.
- _ext.js falls back to DNS TXT payload retrieval from wel1.ru domains.
- Downloaded bytes are written to /var/tmp or temp, chmodded, and detached-spawned via shell/cmd.
- No payload hash is verified despite the integrity-check comment.
- package.json has no lifecycle scripts.
- lib/telemetry.js is not imported by the public entrypoint.
Source & flagged code
4 flagged · loading sourceA package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_ext.jsView on unpkg · L6Findings
Affected versions and remediation
This report applies to claims-person-api-adapters@35.2.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing claims-person-api-adapters@35.2.4. 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.