Which versions of paysafe-venmo are malicious?

The following npm versions of paysafe-venmo are flagged malicious: 99.0.0, 99.99.2. Treat any of these as compromised.

How do I remediate paysafe-venmo if I installed it?

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

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

Yes — paysafe-venmo is associated with the GHSA-5rh7-2mgf-g569 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 paysafe-venmo 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 paysafe-venmo (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging paysafe-venmo across your stack and pipelines.

Malicious package

paysafe-venmonpm

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

MAL-2026-2554

Immediate action

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

npm uninstall paysafe-venmo

What this malware does

The package paysafe-venmo 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 'paysafe-venmo' @ 99.99.2 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

2 flagged

99.0.099.99.2

Indicators of compromise (SHA-256)

00af70e582a340a556d59f45e0a8c06a24a5448fab594e093787f300c8ae6c71

678a8d684fa9e6f72f98c45d404c3e749491bd582d4b78ddc4bc3d020ae3c172

c42be30f22b620a4b1a101e741e5693932681bcc991d08db0b88146edf1a6a63

0fce8d34aa19e18a627c71bd9fd4d16246319ca05abafd983708a534663a573f

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

Campaign

GHSA-5rh7-2mgf-g569

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks paysafe-venmo-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