claims-payout-offer-domain
Claims payout offer domain abstraction layer
This report shows the evidence for claims-payout-offer-domain@35.6.1, 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 confirmed import-time downloader-and-executor, not ordinary telemetry. No lifecycle hook is needed because the package entrypoint activates it.
Decision evidence
public snapshot- index.js imports _vendor on every package import.
- _vendor.js downloads platform payloads from four Workers hosts, with DNS TXT fallback.
- _vendor.js writes payloads under /var/tmp or Windows Temp, chmods Unix payloads, then detached-spawns them.
- The download/execute chain is hidden behind telemetry naming and errors are suppressed.
- package.json has no lifecycle hooks.
- index.js otherwise only exposes a small domain wrapper.
- lib/telemetry.js loader requires explicit run(opts), unlike _vendor.js.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
_vendor.jsView on unpkg · L6A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_vendor.jsView on unpkg · L6Findings
Affected versions and remediation
This report applies to claims-payout-offer-domain@35.6.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing claims-payout-offer-domain@35.6.1. 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.