devplatform-api-v2-resources-metadata
service client SDK
This report shows the evidence for devplatform-api-v2-resources-metadata@35.7.7, 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 concrete import-time remote payload execution, not ordinary SDK telemetry. The package has no lifecycle hook, but the main entrypoint reaches the malicious chain automatically.
Decision evidence
public snapshot- index.js imports _platform.js on every package import.
- _platform.js downloads platform payloads from obfuscated workers.dev hosts.
- _platform.js falls back to DNS TXT payload retrieval from wel1.ru.
- Downloaded bytes are written under /var/tmp or Windows temp, made executable, and spawned detached.
- Import-time execution is suppressed only by telemetry-style opt-out variables.
- package.json has no lifecycle hooks.
- No package-owned source file is read for credentials or secrets.
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.jsView on unpkgPackage source references weak cryptographic algorithms.
lib/telemetry.jsView on unpkg · L27A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_platform.jsView on unpkg · L3Findings
Affected versions and remediation
This report applies to devplatform-api-v2-resources-metadata@35.7.7.
The versions list below shows the verdict for each recorded version.
- Avoid installing devplatform-api-v2-resources-metadata@35.7.7. 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.