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

@postman/secret-scanner-wasmnpm

Advisory published Updated

@postman/secret-scanner-wasm is a confirmed malicious npm package (MAL-2025-190911) that steals credentials and exfiltrates sensitive data (malicious versions 2.1.2, 2.1.3, 2.1.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @postman/secret-scanner-wasm (npm)

MAL-2025-190911
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @postman/secret-scanner-wasm

What this malware does

The package @postman/secret-scanner-wasm was found to contain malicious code.

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

3 flagged
2.1.22.1.32.1.4

Indicators of compromise (SHA-256)

b5d1604689ef91985fbc1fe9f8958eb7a50835e71b7cfa4125de687ca37c2d19
aeaf6631b3409ae49d11b7e96c45997d0f7de1d8d4d76fe181681c12d53ed6a9
16cb0383f876a5cac0dce83e4be06699edbe5282c5f544c0f044d799b770c474

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @postman/secret-scanner-wasm (3 malicious versions).

  2. If you installed it — respond

    @postman/secret-scanner-wasm 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 @postman/secret-scanner-wasm 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. @postman/secret-scanner-wasm on npm has been identified as a malicious package (versions 2.1.2, 2.1.3, 2.1.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06038

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@postman/secret-scanner-wasm (npm) malicious package — MAL-2025-190911 | O3 Security