Which versions of passport811 are malicious?

The following npm versions of passport811 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate passport811 if I installed it?

passport811 is a typosquat — you almost certainly intended a legitimately-named package. Remove passport811, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

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

Yes — passport811 is associated with the GHSA-hqm8-hrc2-wr63, IN-MAL-2026-017438 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 passport811 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 passport811 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging passport811 across your stack and pipelines.

Malicious package

passport811npm

passport811 is a confirmed malicious npm package (MAL-2026-13832) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in passport811 (npm)

MAL-2026-13832

Immediate action

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

npm uninstall passport811

What this malware does

[email protected] contains a single HTML file that impersonates a Cloudflare Turnstile 'Just a moment...' challenge. After the Turnstile callback fires, obfuscated JavaScript assembles a redirect URL to the Microsoft typosquat host microsofte.live (host string built at runtime from an obfuscator.io string-array lookup concatenated with the fragments 'ypt.micros' and 'ofte.live/') and calls window.location.replace() to send the browser there, forwarding the current query string. The package has no library or CLI surface and no lifecycle scripts — the HTML is not executed by npm install or by require(). The artifact is a hosted phishing kit distributed via the npm registry rather than code that attacks the machine performing the install.

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

Indicators of compromise (SHA-256)

b07dbba124b1abdf1e259a2d0233f2ac598111d06892529c8036851ae957b4ba

e96b8ce5a6dee87674b66e3aad6e3cf750c6e24243dd564922ff7b68be2f48b8

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for passport811 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging passport811 across your stack and pipelines.
If you installed it — respond
passport811 is a typosquat — you almost certainly intended a legitimately-named package. Remove passport811, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If passport811 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 passport811 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. passport811 on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-hqm8-hrc2-wr63IN-MAL-2026-017438

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks passport811-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