MAL-2026-12126 Malicious code in a.poltoradnev-package-b (npm)
Malicious package
Published
MAL-2026-12126 is a malicious package: a.poltoradnev-package-b (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-12126/ (Markdown: https://insights.sbomify.com/MAL-2026-12126/index.md)
- Package
- a.poltoradnev-package-b
- Registry
- npm
What is MAL-2026-12126?
MAL-2026-12126 is a malicious package in a.poltoradnev-package-b, published on 5 Aug 2026.
Official description
On require() of the package, index.js loads bridge.js which selects a platform-specific output path, fetches an opaque binary over HTTPS from Cloudflare Workers hosts whose names are assembled from split string fragments (oob-worker.cf100-4.16.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev), writes it to /var/tmp/.cache<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmods 0755, and spawns it detached via /bin/sh -c or cmd. A DNS-TXT fallback channel reconstructs a base64 payload from numbered subdomains under tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site when the HTTPS fetch fails. Destination hostnames are constructed at runtime via Array.join on split fragments to evade static analysis. The written binary is unpinned, unsigned, and unverified, and the code path fires as an import-time side effect rather than through any explicit user action; cover-story identifiers (analytics_state, dotnet_diag_, a DISABLE_TELEMETRY gate) do not correspond to installer-configured behavior.
What should I do about MAL-2026-12126?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.