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

dolyame-ui-inputcolornpm

Advisory published Updated

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

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

What this malware does

index.js unconditionally requires./loader on load. loader.js assembles attacker hostnames at runtime via array.join to hide them from static scanners (e.g., ["oob-w","orker",".cf","101-adf.workers.","de","v"].join("")), selects an OS-specific endpoint, and fetches a binary payload over HTTPS from one of four oob-worker.cf10[0-3]-*.workers.dev hosts. On HTTPS failure, it falls back to a DNS-TXT covert channel: it queries chunked TXT records under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru, base64-concatenates the chunks, and reconstitutes the payload buffer. The bytes are written to /tmp or %TEMP% under a disguised name (.cache<hex> on Unix, dotnet_diag<hex>.exe on Windows), chmodded to 0755, and spawned detached via /bin/sh -c or cmd. Module names, API names, and hostnames are reconstructed via string concatenation and dynamic property access (require("child_" + "process"), fs["chmod" + "Sync"], os["host" + "name"]) to defeat plain-text matching. The dropper fires on every require() of this package, granting the operator of those hosts arbitrary code execution on any machine that installs or imports it.

Malicious versions

1 flagged
35.8.1

Indicators of compromise (SHA-256)

abd621d8f38bf9cc61f7de47b10d8ef68fe086c42508366989552992e0bb8238

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove dolyame-ui-inputcolor 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-inputcolor 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-inputcolor 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-016899

References

Credits

  • Amazon Inspector · finder

Detect & block this

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