Which versions of dontawesome are malicious?

The following npm versions of dontawesome are flagged malicious: 1.1.1, 1.1.4, 8.7.6. Treat any of these as compromised.

How do I remediate dontawesome if I installed it?

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

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

Yes — dontawesome is associated with the RLMA-2026-05040, RLUA-2026-06176 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 dontawesome across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dontawesome (3 malicious versions).

Malicious package

dontawesomenpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

dontawesome is a confirmed malicious npm package (MAL-2026-7251) that executes malicious code on install (malicious versions 1.1.1, 1.1.4, 8.7.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dontawesome (npm)

MAL-2026-7251

Immediate action

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

npm uninstall dontawesome

Malicious versions

3 flagged

1.1.11.1.48.7.6

Indicators of compromise (SHA-256)

0208398a58afabb4c5a479b6ea8fb34dc2697b02861e9205967403d0a4fcf356

018db4c31913eb6494ce7b5d4caa4051871dc15badbacbf79ef4491a3c7500b1

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05040RLUA-2026-06176

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks dontawesome-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