MAL-2026-12697 Malicious code in devplatform-api-v2-resources-metadata (npm)
Malicious package
Published
MAL-2026-12697 is a malicious package: devplatform-api-v2-resources-metadata (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-12697/ (Markdown: https://insights.sbomify.com/MAL-2026-12697/index.md)
- Package
- devplatform-api-v2-resources-metadata
- Registry
- npm
What is MAL-2026-12697?
MAL-2026-12697 is a malicious package in devplatform-api-v2-resources-metadata, published on 5 Aug 2026.
Official description
Package presents itself as a REST API client wrapper, but requiring it loads platform.js which detects the host OS/architecture, fetches a platform-matched native binary from three string-concatenation-obfuscated Cloudflare Workers mirrors (oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS-TXT chunked base64 fallback under sdk/ext/pkg/net.dl.wel1.ru, writes it to /var/tmp or %TEMP% under disguised names (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. An mtime lockfile at /tmp/.analytics_state gates re-triggering. Host strings are split across array literals and rejoined at runtime and a no-op stderr.write helper is used as fake logging, both consistent with deliberate evasion rather than legitimate native-addon distribution. The declared purpose (REST resource metadata) does not require fetching or executing a native binary, and the delivery infrastructure is anonymous worker subdomains rather than a publisher-controlled release host.
What should I do about MAL-2026-12697?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.