Which versions of qa-egs-rollback are malicious?

The following npm versions of qa-egs-rollback are flagged malicious: 0.0.1-security, 1.0.0. Treat any of these as compromised.

How do I remediate qa-egs-rollback if I installed it?

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

If qa-egs-rollback 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.

How do I find qa-egs-rollback across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for qa-egs-rollback (2 malicious versions).

Malicious package

qa-egs-rollbacknpm

Advisory published Oct 30, 2025Updated Oct 1, 2026

qa-egs-rollback is a confirmed malicious npm package (MAL-2025-49235) that executes malicious code on install (malicious versions 0.0.1-security, 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in qa-egs-rollback (npm)

MAL-2025-49235

Immediate action

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

npm uninstall qa-egs-rollback

What this malware does

The package qa-egs-rollback was found to contain malicious code.

Malicious versions

2 flagged

0.0.1-security1.0.0

Indicators of compromise (SHA-256)

f069cbe096962a4415247fec584da742da87006805e2e0a12d2e0a080936479d

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks qa-egs-rollback-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