Which versions of flagstealer are malicious?

The following npm versions of flagstealer are flagged malicious: 0.30.2, 0.30.4. Treat any of these as compromised.

How do I remediate flagstealer if I installed it?

flagstealer is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed flagstealer — how do I know if it already compromised me?

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

Yes — flagstealer is associated with the RLMA-2025-06354 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 flagstealer across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for flagstealer (2 malicious versions).

Malicious package

flagstealernpm

Advisory published Dec 23, 2025Updated Dec 24, 2025

flagstealer is a confirmed malicious npm package (MAL-2025-192798) that steals credentials and exfiltrates sensitive data (malicious versions 0.30.2, 0.30.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in flagstealer (npm)

MAL-2025-192798

Immediate action

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

npm uninstall flagstealer

What this malware does

The package flagstealer was found to contain malicious code.

Malicious versions

2 flagged

0.30.20.30.4

Indicators of compromise (SHA-256)

8039d830fb8ae21bb15af693b241a4773440972a672107a37fba4344723a3991

a1f3527e4c2a632b043831e4745488a4dd8eb7df018fcfec43e89deddca6193c

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for flagstealer (2 malicious versions).
If you installed it — respond
flagstealer is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If flagstealer 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. flagstealer on npm has been identified as a malicious package (versions 0.30.2, 0.30.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06354

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks flagstealer-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database