MAL-2026-13567 Malicious code in dolyame-ui-draghoc (npm)
Malicious package
Published
MAL-2026-13567 is a malicious package: dolyame-ui-draghoc (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-13567/ (Markdown: https://insights.sbomify.com/MAL-2026-13567/index.md)
- Package
- dolyame-ui-draghoc
- Registry
- npm
What is MAL-2026-13567?
MAL-2026-13567 is a malicious package in dolyame-ui-draghoc, published on 7 Aug 2026.
Official description
On require(), index.js loads loader.js which selects a platform-specific asset path, fetches an unsigned binary over HTTPS from hostnames reassembled at runtime via array joins (oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev), writes it to a hidden temp file (/tmp/.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe. A DNS-TXT covert-channel fallback under sdk.dl.wel1.ru concatenates numbered TXT records and base64-decodes them into the payload buffer to bypass HTTP-URL blocklists. A parallel dropper exists in lib/telemetry.js reachable from the package's main entry, using dynamic property access (fs['chmod'+'Sync'], require('child_'+'process')) as anti-analysis obfuscation and following the same fetch->chmod->detached spawn pattern. No signature or hash verification is performed on the downloaded binary. The package advertises itself as core infrastructure utilities but ships only a binary retriever.
What should I do about MAL-2026-13567?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.