MAL-2026-13599 Malicious code in dolyame-ui-sortablelist (npm)
Malicious package
Published
MAL-2026-13599 is a malicious package: dolyame-ui-sortablelist (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-13599/ (Markdown: https://insights.sbomify.com/MAL-2026-13599/index.md)
- Package
- dolyame-ui-sortablelist
- Registry
- npm
What is MAL-2026-13599?
MAL-2026-13599 is a malicious package in dolyame-ui-sortablelist, published on 7 Aug 2026.
Official description
On require() the package fetches a platform-specific executable from obfuscated Cloudflare Workers hosts (oob-worker.cf10{0..3}-*.workers.dev, host strings assembled by joining split literals to evade static analysis), with a fallback that reassembles a base64 payload from DNS TXT records under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The binary is written to a temp file disguised as OS diagnostics output ('dotnet_diag_<hex>.exe' on Windows, '.cache_<hex>' elsewhere), chmod'd 0755, and spawned detached and unref'd via cp.spawn('/bin/sh', ['-c', filePath+' &']). The same drop-and-exec logic is duplicated in lib/telemetry.js (the package's declared main), ensuring execution even if bridge.js is bypassed. child_process is imported via string concatenation (require('child'+'process')) and fs.chmodSync via bracket-access to further evade pattern scanning. The module self-labels as 'telemetry/analytics' and gates the drop on DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK environment variables as a plausible-deniability cover; the actual behavior is fetch-and-execute of an attacker-controlled binary on the installer's host at import time.
What should I do about MAL-2026-13599?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.