Which versions of @postman/node-keytar are malicious?

The following npm versions of @postman/node-keytar are flagged malicious: 7.9.4, 7.9.5, 7.9.6. Treat any of these as compromised.

How do I remediate @postman/node-keytar if I installed it?

@postman/node-keytar 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/node-keytar — how do I know if it already compromised me?

If @postman/node-keytar 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/node-keytar part of a known attack campaign?

Yes — @postman/node-keytar is associated with the GHSA-wwwq-xpmw-9m2m 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/node-keytar 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/node-keytar (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/node-keytar across your stack and pipelines.

Malicious package

@postman/node-keytarnpm

Malicious code in @postman/node-keytar (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190754

Immediate action

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

npm uninstall @postman/node-keytar

What this malware does

The package @postman/node-keytar 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

3 flagged

7.9.47.9.57.9.6

Indicators of compromise (SHA-256)

5f183283a0bd37c933049b6e3a1d6d3e3819c85d4cab5e81874c3ced6c48c83a

4f4c8023740ffdaef4872c662f4f7be6f3258a479dfb93494adda9c170fa4818

505b9a898c902c096cecf18d871dd3a6b2eb4770c4cbdfa13549a0abe2b4ac07

14c788750f7a96d52d68cc858e3216213529762383c470ba82c471b20f1be5f3

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/node-keytar (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/node-keytar across your stack and pipelines.
If you installed it — respond
@postman/node-keytar 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/node-keytar 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/node-keytar 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/node-keytar on npm has been identified as a malicious package (versions 7.9.4, 7.9.5, 7.9.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wwwq-xpmw-9m2m

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @postman/node-keytar-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