devplatform-hooks
Devplatform hooks abstraction layer
This report shows the evidence for devplatform-hooks@35.2.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-aiSource inspection confirms a reachable staged payload loader and executor, not ordinary telemetry. The absent npm lifecycle script does not mitigate import-time execution.
Decision evidence
public snapshot- index.js imports _init.js on every package import.
- _init.js downloads platform-specific binary data from concealed workers.dev hosts.
- _init.js falls back to DNS TXT payload retrieval from wel1.ru domains.
- Downloaded bytes are written to temp storage, chmodded on Unix, then detached-spawned through /bin/sh or cmd.exe.
- No lifecycle hook is needed: normal require/import triggers the payload chain.
- package.json declares no install lifecycle scripts.
- No credential or environment-value exfiltration was found in the reachable loader.
Source & flagged code
4 flagged · loading sourceA package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_init.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to devplatform-hooks@35.2.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing devplatform-hooks@35.2.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.