Which versions of capacitor-purchase-history are malicious?

The following npm versions of capacitor-purchase-history are flagged malicious: 0.0.10. Treat any of these as compromised.

How do I remediate capacitor-purchase-history if I installed it?

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

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

Yes — capacitor-purchase-history is associated with the GHSA-6wfp-gm7m-4vcw 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 capacitor-purchase-history across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for capacitor-purchase-history (version 0.0.10).

Malicious package

capacitor-purchase-historynpm

Advisory published Nov 24, 2025Updated Nov 26, 2025

capacitor-purchase-history is a confirmed malicious npm package (MAL-2025-190766) that steals credentials and exfiltrates sensitive data (malicious version 0.0.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in capacitor-purchase-history (npm)

MAL-2025-190766

Immediate action

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

npm uninstall capacitor-purchase-history

What this malware does

The package capacitor-purchase-history 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

0.0.10

Indicators of compromise (SHA-256)

9290201e4d35791cd39bebd58faaa5e9885156bac7a8c31882fb29ceae3f6cd9

9ef54df7bce3add5d55de2f91510b75ffc757c47626010c4f44b59ef8f08242c

539c3b2fafae0bfb8a56f15bae5104736ad9d2d89fdd3c9ca6353c1fb220bc76

Detection & response playbook

Credential / info stealer

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

Campaign

GHSA-6wfp-gm7m-4vcw

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks capacitor-purchase-history-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