Which versions of stacknova are malicious?

The following npm versions of stacknova are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate stacknova if I installed it?

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

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

Yes — stacknova is associated with the GHSA-5cpm-r2cm-wpjc, RLMA-2026-05322, RLUA-2026-06510 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 stacknova across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for stacknova (version 1.0.0).

Malicious package

stacknovanpm

Advisory published Jul 6, 2026Updated Sep 1, 2026

stacknova is a confirmed malicious npm package (MAL-2026-6882) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in stacknova (npm)

MAL-2026-6882

Immediate action

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

npm uninstall stacknova

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

4eea780e4546d725f38c35c635625e60354e7f48a79c1fcbe76f87e2498d9ce4

c2a8a209f5b49235728ca09df05c23ead3143109ae0f50d8b68b64d212c9b7c9

b4a8a49f9ce331c49a1ffa7fcd35adf86a631a09f5f941c2dbec0b24bc18bcd6

Detection & response playbook

Malicious package

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

Campaign

GHSA-5cpm-r2cm-wpjcRLMA-2026-05322RLUA-2026-06510

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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