Which versions of ally-antivirus are malicious?

The following npm versions of ally-antivirus are flagged malicious: 99.99.99, 100.0.0. Treat any of these as compromised.

How do I remediate ally-antivirus if I installed it?

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

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

Yes — ally-antivirus is associated with the GHSA-fxqc-33g9-rh7j 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 ally-antivirus 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 ally-antivirus (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ally-antivirus across your stack and pipelines.

Malicious package

ally-antivirusnpm

Malicious code in ally-antivirus (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3295

Immediate action

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

npm uninstall ally-antivirus

What this malware does

The package ally-antivirus 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.

The OpenSSF Package Analysis project identified 'ally-antivirus' @ 99.99.99 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

99.99.99100.0.0

Indicators of compromise (SHA-256)

77bb25e7bd9ff8b0847c8b9faeae5663340fc87828e3614a96568c5580b0a45d

da1c12572226f81d6eaabc293eea0517dbaac2153885aba08cd68c3408896c99

7e5527c47f32b162abebfbbb8a15c8871ef050e5e0b07f8096b573cab2e6dfec

094da0aa0245426ad224e9b2a072377a3c07bfc191bc3fab1d2060cdeaf79387

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ally-antivirus (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ally-antivirus across your stack and pipelines.
If you installed it — respond
Remove ally-antivirus 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 ally-antivirus 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 ally-antivirus 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. ally-antivirus on npm has been identified as a malicious package (versions 99.99.99, 100.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-fxqc-33g9-rh7j

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks ally-antivirus-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