Which versions of dolyame-ui-codemods are malicious?

The following npm versions of dolyame-ui-codemods are flagged malicious: 35.2.6. Treat any of these as compromised.

How do I remediate dolyame-ui-codemods if I installed it?

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.

I already installed dolyame-ui-codemods — how do I know if it already compromised me?

If dolyame-ui-codemods 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.

Is dolyame-ui-codemods part of a known attack campaign?

Yes — dolyame-ui-codemods is associated with the IN-MAL-2026-015636 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find dolyame-ui-codemods across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dolyame-ui-codemods (version 35.2.6).

Malicious package

dolyame-ui-codemodsnpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

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

Find it
Search your lockfiles and build artifacts for dolyame-ui-codemods (version 35.2.6).
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.
Did it already run?
If dolyame-ui-codemods 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-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

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database