Which versions of @postman/tunnel-agent are malicious?

The following npm versions of @postman/tunnel-agent are flagged malicious: 0.6.5, 0.6.6, 0.6.7. Treat any of these as compromised.

How do I remediate @postman/tunnel-agent if I installed it?

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

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

Yes — @postman/tunnel-agent is associated with the GHSA-wrhq-7m36-c43f 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/tunnel-agent 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/tunnel-agent (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/tunnel-agent across your stack and pipelines.

Malicious package

@postman/tunnel-agentnpm

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

MAL-2025-190647

Immediate action

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

npm uninstall @postman/tunnel-agent

What this malware does

The package @postman/tunnel-agent 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

0.6.50.6.60.6.7

Indicators of compromise (SHA-256)

b22d1ad5660a0962f206d2473447e9f0581cbc5f2305727a90193249c3a624bf

6961dafcc910bb7a6b1db8cb597068eeb85f973dcd669392354a7b614928dbf5

e93d7934ec491b9f2b476608b71f5e2526d26ddb935bfb724ec73c12ab1225a2

9b313f361e3b72098292bf2cc5691d779dee811c84b580b0f405f016ba779b85

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

Campaign

GHSA-wrhq-7m36-c43f

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @postman/tunnel-agent-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