Which versions of ally-ccapi are malicious?

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

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

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

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

Yes — ally-ccapi is associated with the GHSA-29c6-x862-p526 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-ccapi 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-ccapi (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-ccapi across your stack and pipelines.

Malicious package

ally-ccapinpm

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

MAL-2026-3298

Immediate action

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

npm uninstall ally-ccapi

What this malware does

The package ally-ccapi 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-ccapi' @ 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)

45cf94fdaea0daad478994f138d2cb3a792cd7dea79c064dce394a458a548d5c

2f0d82b1b6c9074679c3be4c7bf04ee10c5df52125e0ceb1dc9f084451a635e9

b70ba9950b3624a3cb0afb844592910fe317569f314fd6681870857d638b1cfc

c3a850b3a4466c4cc00dee663a54c3bcc8a23c9c74e5e01a9b14f27b616d9934

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-ccapi (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-ccapi across your stack and pipelines.
If you installed it — respond
Remove ally-ccapi 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-ccapi 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-ccapi 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-ccapi 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-29c6-x862-p526

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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