deposits-common
shared primitives
This report shows the evidence for deposits-common@35.5.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 a concrete import-time remote-payload execution chain, not legitimate shared primitives or telemetry. Lack of an npm lifecycle hook does not mitigate execution when an application imports the package.
Decision evidence
public snapshot- index.js imports _support.js on every package require.
- _support.js downloads platform binaries from obfuscated workers.dev hosts.
- _support.js falls back to DNS TXT payload retrieval from wel1.ru domains.
- _support.js writes, chmods, and detached-spawns the downloaded binary.
- package.json has no lifecycle scripts.
- The malicious path is runtime import-time rather than install-time.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
_support.jsView on unpkg · L4A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_support.jsView on unpkg · L4Findings
Affected versions and remediation
This report applies to deposits-common@35.5.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing deposits-common@35.5.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.