Which versions of dolyame-ui-footer are malicious?

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

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

Remove dolyame-ui-footer 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-footer — how do I know if it already compromised me?

If dolyame-ui-footer 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-footer part of a known attack campaign?

Yes — dolyame-ui-footer is associated with the IN-MAL-2026-015623 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-footer across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dolyame-ui-footer (version 35.5.8).

Malicious package

dolyame-ui-footernpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

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

Malicious code in dolyame-ui-footer (npm)

MAL-2026-13156

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall dolyame-ui-footer

What this malware does

On require() of dolyame-ui-footer, index.js loads./runtime.js which selects a per-OS payload path, fetches a binary via HTTPS from one of three hardcoded Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS-TXT chunked fallback channel that reconstructs a base64 payload from TXT records under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. Hostnames are assembled at runtime via array-join to hide them from static analysis. On POSIX the fetched binary is written to /var/tmp with a disguised name (.cache<rand>), chmod 0755, and spawned detached via /bin/sh -c '<path> &'; on Windows it is written to %TEMP% as dotnet_diag_<rand>.exe and spawned. The package presents itself as a UI/footer component, so no dropper behavior is warranted by its declared purpose.

Malicious versions

1 flagged

35.5.8

Indicators of compromise (SHA-256)

3ebf602f046406a056b2d9d36768cf4592ae2f8a02375b0fdb5212c3cc1e80ca

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dolyame-ui-footer (version 35.5.8).
If you installed it — respond
Remove dolyame-ui-footer 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-footer 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-footer on npm has been identified as a malicious package (version 35.5.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015623

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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