Which versions of passtpor are malicious?

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

How do I remediate passtpor if I installed it?

Remove passtpor 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 passtpor — how do I know if it already compromised me?

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

Yes — passtpor is associated with the GHSA-j9c9-vv76-9f83, RLMA-2026-06364, RLUA-2026-10772 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 passtpor across my projects, lockfiles, and CI pipelines?

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

Malicious package

passtpornpm

Advisory published Jul 31, 2026Updated Sep 24, 2026

passtpor is a confirmed malicious npm package (MAL-2026-11345) 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 passtpor (npm)

MAL-2026-11345

Immediate action

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

npm uninstall passtpor

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)

1e427a84573f9d6512d302e4f8ffc7c1011e5b9d337f4b084da29c797ce25b9e

74e28a02a2111fbf798ba5ebe582716d47c80af28b08096474c7f26aa63d9b33

163b644b5ae88d3ed7b0cdd3a8d12ed555d1b81f3714ab6c0d7af57f5b1ae8ff

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for passtpor (version 1.0.1).
If you installed it — respond
Remove passtpor 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 passtpor 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. passtpor 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-j9c9-vv76-9f83RLMA-2026-06364RLUA-2026-10772

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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