MAL-2026-13202 Malicious code in dwhetlfront-dwhetlfront-core (npm)
Malicious package
Published
MAL-2026-13202 is a malicious package: dwhetlfront-dwhetlfront-core (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-13202/ (Markdown: https://insights.sbomify.com/MAL-2026-13202/index.md)
- Package
- dwhetlfront-dwhetlfront-core
- Registry
- npm
What is MAL-2026-13202?
MAL-2026-13202 is a malicious package in dwhetlfront-dwhetlfront-core, published on 5 Aug 2026.
Official description
On require() of the package, index.js loads support.js which selects a platform-specific payload URL, downloads bytes from Cloudflare workers.dev hosts (oob-worker.cf10{0-3}-*.workers.dev) with a DNS-TXT chunked-base64 fallback under {sdk,ext,pkg,net}.dl.wel1.ru, writes the bytes to /tmp or %TEMP% under a cover-story filename (dotnet_diag.exe,.cache_), chmods 0755, and spawns the file detached via cp.spawn('/bin/sh', ['-c', path + ' &'], {detached:true}) or spawn('cmd',…). Destination hostnames are reconstructed at runtime via array-join splits (e.g., ['sdk','.d','l.wel1','.r','u'].join('') and ['oob-w','orker.cf100-416.worker','s.','dev'].join('')) and API names such as 'child_' + 'process' are string-concatenated to evade static analysis. A lock file gates repeat execution and an opt-out env var serves as a cover story. A parallel dropper implementation exists in lib/telemetry.js (base64 chunk assembly, sh -c spawn, chmod 755 via bracketed 'chmod'+'Sync'); it is not reached from index.js in this version but is bundled in the tarball.
What should I do about MAL-2026-13202?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.