devplatform-npm-versions-checker
Devplatform npm versions checker provider for microservice architecture
This report shows the evidence for devplatform-npm-versions-checker@35.5.9. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
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 import-time remote payload execution, not package-aligned version-checking or benign telemetry. Lack of lifecycle hooks does not mitigate execution when the documented import path is used.
Decision evidence
public snapshot- index.js imports _adapter.js at module load.
- _adapter.js downloads platform payloads over HTTPS and DNS TXT.
- _adapter.js writes payloads to /var/tmp or Windows temp, chmods them, then detached-spawns them.
- Payload hosts are obfuscated workers.dev domains; DNS fallback uses wel1.ru.
- No checksum, signature, or user action gates remote binary execution.
- lib/telemetry.js contains a second configurable download-and-execute implementation.
- package.json has no lifecycle scripts.
- Opt-out environment variables can prevent _adapter.js execution.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
_adapter.jsView on unpkg · L4A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_adapter.jsView on unpkg · L4Findings
Affected versions and remediation
This report applies to devplatform-npm-versions-checker@35.5.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing devplatform-npm-versions-checker@35.5.9. 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.