Which versions of @augmentor/experiences are malicious?

Every published version of @augmentor/experiences on npm is considered malicious. Remove the package entirely.

How do I remediate @augmentor/experiences if I installed it?

@augmentor/experiences 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 @augmentor/experiences — how do I know if it already compromised me?

If @augmentor/experiences was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @augmentor/experiences part of a known attack campaign?

Yes — @augmentor/experiences is associated with the GHSA-mpxg-x386-qhgr 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 @augmentor/experiences across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @augmentor/experiences (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @augmentor/experiences across your stack and pipelines.

Malicious package

@augmentor/experiencesnpm

Malicious code in @augmentor/experiences (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1317

Immediate action

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

npm uninstall @augmentor/experiences

What this malware does

Malware detected: Collects and exfiltrates sensitive data to a suspicious webhook via a preinstall script.

The package @augmentor/experiences 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)

f754f861d02ac278fdb8ef5ecb6085ffc554d62b142107db51d21ca74b8ac48b

4067e28e3de3f031541a3e624d8d21dc75777b65b83ab8aa4fd09bfd52038968

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @augmentor/experiences (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @augmentor/experiences across your stack and pipelines.
If you installed it — respond
@augmentor/experiences 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 @augmentor/experiences was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @augmentor/experiences before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @augmentor/experiences 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-mpxg-x386-qhgr

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks @augmentor/experiences-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