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

dolyame-ui-codemodsnpm

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

Malicious code in dolyame-ui-codemods (npm)

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

What this malware does

On require('dolyame-ui-codemods'), index.js loads _polyfill.js, which reconstructs remote hostnames from split string-fragment arrays joined at runtime (assembling oob-worker.*.workers.dev subdomains and sdk/ext/pkg/net.dl.wel1.ru), selects a platform-specific endpoint, downloads a binary over HTTPS, writes it to /var/tmp or %TEMP% under a disguised name resembling dotnet_diag, chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe. A DNS-TXT-record fallback channel retrieves chunked base64 payloads from numbered subdomains of dl.wel1.ru when HTTPS delivery fails. A cooldown stamp file suppresses repeat execution and environment-variable checks gate execution to evade sandboxes. The package is advertised as a UI toolkit and has no legitimate need for a platform-native binary, obfuscated hostname assembly, or a DNS covert channel. Installing or importing this package causes remote code execution on the host.

Malicious versions

1 flagged
35.2.6

Indicators of compromise (SHA-256)

aa4592f76ef0995b4e3c8b0cc15c00862cf594cbaebbfcd2bf25d2640bbf6012

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-codemods (version 35.2.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-codemods across your stack and pipelines.

  2. If you installed it — respond

    Remove dolyame-ui-codemods 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-codemods 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-codemods 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-codemods on npm has been identified as a malicious package (version 35.2.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015636

References

Credits

  • Amazon Inspector · finder

Detect & block this

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