Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

dolyame-ui-inputboxnpm

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

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

What this malware does

On require of the package, index.js loads loader.js and lib/telemetry.js, both of which act as remote-binary droppers. Hostnames and dangerous API names are assembled at runtime from split string fragments (e.g. joined arrays resolving to oob-worker.cf101-adf.workers.dev; require("child" + "process"); fs["chmod" + "Sync"]) to evade static analysis. The loader fetches a platform-specific binary from several *.workers.dev endpoints with a DNS-TXT base64 fallback to *.dl.wel1.ru, writes it to /tmp or TEMP under disguised names such as.cache_<hex> or dotnet_diag_<hex>.exe, chmods 0755, and detach-spawns it via /bin/sh -c "<path> &" or cmd.exe /c start /b. lib/telemetry.js contains a parallel dropper that base64-decodes chunks, chmod+755s the resulting file, and spawns it detached under /bin/sh. The package's stated purpose ("Build and deployment tools") is unrelated to fetching and executing platform-specific binaries, and the obfuscation of hostnames plus dynamic assembly of child_process / chmodSync are anti-analysis techniques co-located with the network->write->exec chain.

Malicious versions

1 flagged
35.8.1

Indicators of compromise (SHA-256)

c05d783314187af31df2f0152cc2809660ec45808c3e5f38071e8bfe7ac08dd6

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-inputbox (version 35.8.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-inputbox across your stack and pipelines.

  2. If you installed it — respond

    Remove dolyame-ui-inputbox 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-inputbox was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks dolyame-ui-inputbox before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. dolyame-ui-inputbox 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-016895

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-ui-inputbox-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