NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

adyen-web-v5npm

Advisory published Updated

adyen-web-v5 is a confirmed malicious npm package (MAL-2025-50757) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in adyen-web-v5 (npm)

MAL-2025-50757
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall adyen-web-v5

What this malware does

The package adyen-web-v5 was found to contain malicious code. This package appears to be part of the tea.xyz token reward campaign that flooded npm with over 15,000 spam packages in 2024. These packages typically contain autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) designed to automatically generate and publish derivative packages with randomized names to inflate developer reputation scores for tea protocol token rewards. The malicious payload modifies package.json to remove private flags, changes version numbers, generates random Indonesian-themed package names, and continuously republishes variants to pollute the npm registry.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

25b6c05640ee26217a85a428224b5a1a72790f5efec2d036828cb3cda0afa5ab
6dc13df0c80f9ea8431c4125c554ee151d80237fa5e6970c7751f5ec3e520772

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for adyen-web-v5 (all published versions).

  2. If you installed it — respond

    Remove adyen-web-v5 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.

  3. Did it already run?

    If adyen-web-v5 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. adyen-web-v5 on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jcxx-7rcc-8rw7

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks adyen-web-v5-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.

Explore

adyen-web-v5 (npm) malicious package — MAL-2025-50757 | O3 Security