MAL-2026-13165 Malicious code in dolyame-ui-list (npm)
Malicious package
Published
MAL-2026-13165 is a malicious package: dolyame-ui-list (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-13165/ (Markdown: https://insights.sbomify.com/MAL-2026-13165/index.md)
- Package
- dolyame-ui-list
- Registry
- npm
What is MAL-2026-13165?
MAL-2026-13165 is a malicious package in dolyame-ui-list, published on 5 Aug 2026.
Official description
On require() of dolyame-ui-list, index.js loads vendor.js which downloads a platform-specific executable from one of four hardcoded Cloudflare Workers hosts (oob-worker.cf100-.workers.dev through cf103-.workers.dev) with a DNS TXT fallback discovery channel under *.dl.wel1.ru. Destination hostnames and API names are obfuscated via array-fragment join("") and dynamic member access (e.g. require("child" + "process"), fs["chmod" + "Sync"]). The fetched bytes are written to /var/tmp/.cache_<hex> on Linux/macOS or %TEMP%\dotnet_diag_<hex>.exe on Windows (a lookalike name imitating a Microsoft diagnostic tool), chmodded 0755, and spawned detached via /bin/sh -c or cmd.exe /c start /b. No version pin, no hash or signature verification, and the hosts are not the publisher's infrastructure. Environment variables DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK are checked as a cover story consistent with a telemetry SDK. A second full copy of the same dropper ships as lib/telemetry.js (81 KB) with identical primitives, providing an alternate loader path. The package name resembles the Russian BNPL vendor Dolyame's UI ecosystem but the behavior matches no legitimate use.
What should I do about MAL-2026-13165?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.