NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Part of a larger attack: @asyncapi published 36 malicious packages. See the full campaign →
Malicious package

@asyncapi/server-apinpm

Advisory published Updated

@asyncapi/server-api is a confirmed malicious npm package (MAL-2025-190801) that steals credentials and exfiltrates sensitive data (malicious versions 0.16.24, 0.16.25). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @asyncapi/server-api (npm)

MAL-2025-190801
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @asyncapi/server-api

What this malware does

The package @asyncapi/server-api 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

2 flagged
0.16.240.16.25

Indicators of compromise (SHA-256)

a33212db09f9fc4818a054bde0721879323b7e8896b313c33b1af9e136f4d6d8
228ed250759da1a81a55ea29e65821a583726c0c472d925b0c86d4e44e49e002
0e3f81bd867ef35c3fb884d4991f6cee8567951ce526efc4b9dc3ea87372e65b
03d7c62fa12ae91e08912d9153e732577685bde39475c489d90117412ecd1406

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @asyncapi/server-api (2 malicious versions).

  2. If you installed it — respond

    @asyncapi/server-api is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @asyncapi/server-api 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. @asyncapi/server-api on npm has been identified as a malicious package (versions 0.16.24, 0.16.25 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4vf7-5v4w-7358

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @asyncapi/server-api-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@asyncapi/server-api (npm) malicious package — MAL-2025-190801 | O3 Security