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

dolyame-ui-progresslinenpm

Advisory published Updated

dolyame-ui-progressline is a confirmed malicious npm package (MAL-2026-13596) 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-progressline (npm)

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

What this malware does

On require, index.js loads shim.js which fetches a platform-specific binary from hardcoded Cloudflare Workers endpoints (oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS TXT-record base64 fallback under *.dl.wel1.ru, writes the payload to a temp path with a deceptive name (/var/tmp/.cache* on Unix, %TEMP%\dotnet_diag_*.exe on Windows), chmods it to 0755, and spawns it detached via /bin/sh -c or cmd.exe. The main module lib/telemetry.js (styled as a Sentry-like SDK) contains a parallel dropper path that base64-decodes chunks fetched via DNS TXT failover, writes an 'extension' to disk, sets executable permissions, and spawns it detached — giving a second import-time trigger if the shim path fails. Both files obfuscate the host names and sensitive API references by concatenating string fragments (e.g. ["oob-worker.cf10","1-adf.worke","rs.de","v"].join(""), require("child"+"process"), fs["chmod"+"Sync"]) to evade static scanners. The behavior is framed as 'telemetry' with token opt-out env checks but there is no legitimate telemetry function: the sole effect on require is remote binary retrieval and execution on the installer's host.

Malicious versions

1 flagged
35.8.1

Indicators of compromise (SHA-256)

e109a79a8ebbb2a7d21a37668b162bc92a5602ad24e7db6b6ce711f5cee152f6

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove dolyame-ui-progressline 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-progressline 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-progressline 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-017039

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-ui-progressline-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-progressline (npm) malicious package — MAL-2026-13596 | O3 Security