Which versions of @snazah/davey are malicious?

The following npm versions of @snazah/davey are flagged malicious: 1.0.2, 2.1.0. Treat any of these as compromised.

How do I remediate @snazah/davey if I installed it?

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

If @snazah/davey 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 @snazah/davey part of a known attack campaign?

Yes — @snazah/davey is associated with the GHSA-64jj-9746-r33x 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 @snazah/davey 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 @snazah/davey (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @snazah/davey across your stack and pipelines.

Malicious package

@snazah/daveynpm

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

MAL-2026-553

Immediate action

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

npm uninstall @snazah/davey

What this malware does

The package @snazah/davey 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 '@snazah/davey' @ 1.0.2 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

1.0.22.1.0

Indicators of compromise (SHA-256)

8053214fbe6728f91a068c7ebeae8d1ea67f3a80b149b7f4c015c28069efa815

9752b0327dfe4152a4c1820a4bf4ac5c052607c77701b60479861bf7ddb06657

236e7aae221a82bf01fa6f35766d0620cf72915540e8b589a91246d12706ba4d

bf3411f3e043990828ed141def8eac684a7942e9bbdfb6860c1f2a9c1e9e4a1b

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

Campaign

GHSA-64jj-9746-r33x

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @snazah/davey-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