Which versions of flagstealerfinal are malicious?

Every published version of flagstealerfinal on npm is considered malicious. Remove the package entirely.

How do I remediate flagstealerfinal if I installed it?

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

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

Yes — flagstealerfinal is associated with the GHSA-x5xj-9r4p-43cv 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 flagstealerfinal across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for flagstealerfinal (all published versions).

Malicious package

flagstealerfinalnpm

Advisory published Dec 19, 2025Updated Dec 22, 2025

flagstealerfinal is a confirmed malicious npm package (MAL-2025-192629) that steals credentials and exfiltrates sensitive data. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in flagstealerfinal (npm)

MAL-2025-192629

Immediate action

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

npm uninstall flagstealerfinal

What this malware does

The package flagstealerfinal was found to contain malicious code.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

eecc837f74a9e474ce6f056e83fc505b9f1126d18a96a5eb879def906682fdf5

64b9cc9bb0bafe61901221efe8e6c9359eef4061151cc1a35544721addc6b8f2

Detection & response playbook

Credential / info stealer

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

Campaign

GHSA-x5xj-9r4p-43cv

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

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