Which versions of token-verify-passport are malicious?

Every published version of token-verify-passport on npm is considered malicious. Remove the package entirely.

How do I remediate token-verify-passport if I installed it?

token-verify-passport 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 token-verify-passport — how do I know if it already compromised me?

If token-verify-passport 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 token-verify-passport part of a known attack campaign?

Yes — token-verify-passport is associated with the GHSA-gjj2-6wcj-mv3q 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 token-verify-passport 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 token-verify-passport (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging token-verify-passport across your stack and pipelines.

Malicious package

token-verify-passportnpm

Malicious code in token-verify-passport (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190633

Immediate action

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

npm uninstall token-verify-passport

What this malware does

The package token-verify-passport 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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

f72b6d342e19648cd45c5855b4accacd6b530d2bc525748cfe34f8b44a24dd9b

c9e55c841368b86c3afd97dd35da3304c3507470af6aeb1bada98fa128233e03

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 token-verify-passport (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging token-verify-passport across your stack and pipelines.
If you installed it — respond
token-verify-passport 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 token-verify-passport 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 token-verify-passport 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. token-verify-passport on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-gjj2-6wcj-mv3q

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks token-verify-passport-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