MAL-2026-12215 Malicious code in statist-browser-typed-client-sme.salary.web.metrics (npm)
Malicious package
Published
MAL-2026-12215 is a malicious package: statist-browser-typed-client-sme.salary.web.metrics (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-12215/ (Markdown: https://insights.sbomify.com/MAL-2026-12215/index.md)
- Package
- statist-browser-typed-client-sme.salary.web.metrics
- Registry
- npm
What is MAL-2026-12215?
MAL-2026-12215 is a malicious package in statist-browser-typed-client-sme.salary.web.metrics, published on 5 Aug 2026.
Official description
On require(), adapter.js fetches a platform-specific binary payload from split-string-obfuscated Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS-TXT resolver fallback under *.dl.well1.site (tin.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site). The fetched bytes are written to /var/tmp or %TEMP% under cover-story names (.cache<rand> on POSIX, dotnet_diag_<rand>.exe on Windows), chmod 0755'd on POSIX, and spawned detached via /bin/sh or cmd.exe. There is no hash or signature verification of the fetched payload. Endpoint hostnames and resolver domains are reconstructed at runtime by joining literal fragments to evade static string matching. The package presents itself as an observability/metrics bridge, but the shipped behavior on import is download-and-execute of an opaque attacker-controlled binary, giving whoever published this full code execution on any host that installs or imports the package.
What should I do about MAL-2026-12215?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.