NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

dolyame-ui-draghocnpm

Advisory published Updated

dolyame-ui-draghoc is a confirmed malicious npm package (MAL-2026-13567) that executes malicious code on install (malicious version 35.8.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-ui-draghoc (npm)

MAL-2026-13567
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall dolyame-ui-draghoc

What this malware does

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.

Malicious versions

1 flagged
35.8.1

Indicators of compromise (SHA-256)

9b2e12132d37505525293870b3a824831321d42adf75758e949b30139a002955

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for dolyame-ui-draghoc (version 35.8.1).

  2. If you installed it — respond

    Remove dolyame-ui-draghoc from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If dolyame-ui-draghoc was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. dolyame-ui-draghoc on npm has been identified as a malicious package (version 35.8.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016972

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-ui-draghoc-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

dolyame-ui-draghoc (npm) malicious package — MAL-2026-13567 | O3 Security