Which versions of zappr are malicious?

The following npm versions of zappr are flagged malicious: 0.0.1-security, 56.2.1. Treat any of these as compromised.

How do I remediate zappr if I installed it?

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

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

Yes — zappr is associated with the GHSA-6cp7-hh84-q43w, RLMA-2026-01670 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 zappr 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 zappr (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging zappr across your stack and pipelines.

Malicious package

zapprnpm

Malicious code in zappr (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-730

Immediate action

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

npm uninstall zappr

What this malware does

The package zappr 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

2 flagged

0.0.1-security56.2.1

Indicators of compromise (SHA-256)

c770ad9e96af96c9a3d81bf160dcb48c4d3b4e16e5dc6e717e7161d8e3ab420f

cd1d1ba299d9e9b09804199d01b8da2e7f28c9305d8880ed49177a01e9d094f3

5597bf8a2fce92d1dde4eaf54316b2092253b6b4455621f180ead4cba0eaa993

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 zappr (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging zappr across your stack and pipelines.
If you installed it — respond
Remove zappr 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 zappr 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 zappr 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. zappr on npm has been identified as a malicious package (versions 0.0.1-security, 56.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-6cp7-hh84-q43wRLMA-2026-01670

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks zappr-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