Which versions of passsport1 are malicious?

The following npm versions of passsport1 are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate passsport1 if I installed it?

Remove passsport1 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed passsport1 — how do I know if it already compromised me?

If passsport1 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.

Is passsport1 part of a known attack campaign?

Yes — passsport1 is associated with the GHSA-whq9-wwww-4g3q, RLMA-2026-06363, RLUA-2026-10771 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 passsport1 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for passsport1 (version 1.0.1).

Malicious package

passsport1npm

Advisory published Jul 31, 2026Updated Sep 24, 2026

passsport1 is a confirmed malicious npm package (MAL-2026-11344) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in passsport1 (npm)

MAL-2026-11344

Immediate action

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

npm uninstall passsport1

What this malware does

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

1 flagged

1.0.1

Indicators of compromise (SHA-256)

68604126507bac849b697119200b6ef37f408aaa077f208ae0127605159a9832

be140b785c4bb4d95121ab319c11221463b1265c495099f7829af5a4cafbb1ac

1943f35379c6c1d37ee938c9c15860f945ea6ef803c3a4bf07e1398b8a5efa69

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for passsport1 (version 1.0.1).
If you installed it — respond
Remove passsport1 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If passsport1 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. passsport1 on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-whq9-wwww-4g3qRLMA-2026-06363RLUA-2026-10771

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks passsport1-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database