claims-get-base-url
Pluggable claims get base url interface
This report shows the evidence for claims-get-base-url@35.4.5, 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-code-execution chain unrelated to the package's stated base-URL wrapper function. The absence of an npm lifecycle hook does not mitigate execution when consumers load the main entrypoint.
Decision evidence
public snapshot- index.js imports ./setup at module load.
- setup.js downloads an unverified binary from rotating workers.dev hosts.
- setup.js falls back to DNS TXT payload retrieval from wel1.ru domains.
- setup.js writes the payload to a temp path, chmods it, then starts it detached via shell/cmd.
- The import-time path needs no caller opt-in beyond requiring the package.
- package.json contains no npm lifecycle script.
- lib/telemetry.js is not imported by the package entrypoint.
Source & flagged code
5 flagged · loading sourceSource downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27Source file is highly similar to a previously finalized malicious package; route for source-aware review.
lib/telemetry.jsFindings
Affected versions and remediation
This report applies to claims-get-base-url@35.4.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing claims-get-base-url@35.4.5. 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.