Which versions of @postman/secret-scanner-wasm are malicious?

The following npm versions of @postman/secret-scanner-wasm are flagged malicious: 2.1.2, 2.1.3, 2.1.4. Treat any of these as compromised.

How do I remediate @postman/secret-scanner-wasm if I installed it?

@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.

I already installed @postman/secret-scanner-wasm — how do I know if it already compromised me?

If @postman/secret-scanner-wasm 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 @postman/secret-scanner-wasm part of a known attack campaign?

Yes — @postman/secret-scanner-wasm is associated with the RLMA-2025-06038 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 @postman/secret-scanner-wasm 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 @postman/secret-scanner-wasm (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @postman/secret-scanner-wasm across your stack and pipelines.

Malicious package

@postman/secret-scanner-wasmnpm

Malicious code in @postman/secret-scanner-wasm (npm) Remove it immediately and rotate any exposed credentials.

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

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @postman/secret-scanner-wasm (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @postman/secret-scanner-wasm across your stack and pipelines.
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.
Did it already run?
If @postman/secret-scanner-wasm 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 @postman/secret-scanner-wasm 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. @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