MAL-2026-13150 Malicious code in dolyame-ui-container (npm)
Malicious package
Published
MAL-2026-13150 is a malicious package: dolyame-ui-container (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-13150/ (Markdown: https://insights.sbomify.com/MAL-2026-13150/index.md)
- Package
- dolyame-ui-container
- Registry
- npm
What is MAL-2026-13150?
MAL-2026-13150 is a malicious package in dolyame-ui-container, published on 5 Aug 2026.
Official description
On require of the package, index.js loads compat.js, which at module load time downloads a platform-specific binary from hostnames assembled at runtime via string-splitting (oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev). If HTTPS mirrors fail, it falls back to a DNS-over-TXT covert channel, resolving TXT records under *.dl.wel1.ru subdomains and base64-decoding the concatenated response into a binary. The fetched payload is written to a disguised path under /tmp or %TEMP% (e.g. dotnet_diag<hex>.exe,.cache_<hex>), chmod 0755, and spawned detached via cmd.exe or /bin/sh -c with no hash or signature verification. Environment variable checks (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) and analytics-styled filenames provide cover. The destinations are not the publisher's infrastructure and the retrieval mechanism is inconsistent with any legitimate distribution channel.
What should I do about MAL-2026-13150?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.