Which versions of @nestjs-passport/jwt are malicious?

The following npm versions of @nestjs-passport/jwt are flagged malicious: 1.0.4, 1.0.7. Treat any of these as compromised.

How do I remediate @nestjs-passport/jwt if I installed it?

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

I already installed @nestjs-passport/jwt — how do I know if it already compromised me?

If @nestjs-passport/jwt 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 @nestjs-passport/jwt part of a known attack campaign?

Yes — @nestjs-passport/jwt is associated with the IN-MAL-2026-017136, IN-MAL-2026-017135 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 @nestjs-passport/jwt 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 @nestjs-passport/jwt (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @nestjs-passport/jwt across your stack and pipelines.

Malicious package

@nestjs-passport/jwtnpm

@nestjs-passport/jwt is a confirmed malicious npm package (MAL-2026-13627) that typosquats a legitimate package to trick installs (malicious versions 1.0.4, 1.0.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @nestjs-passport/jwt (npm)

MAL-2026-13627

Immediate action

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

npm uninstall @nestjs-passport/jwt

What this malware does

Package published under the @nestjs-passport scope, which resembles the official @nestjs/jwt and @nestjs/passport packages. The sole entrypoint files dist/index.cjs and dist/index.js each consist of a single-line JSFuck-encoded string (~2.3MB of permutations of!+[],!![], +[]) that is passed to new Function('jose', <opaque body>) and invoked at require/import time, executing hidden code in the installer's Node process every time the module is loaded. The advertised purpose is a minimal HS256 JWT helper — a task requiring only a few lines of jose calls — and the shipped TypeScript declarations expose obfuscated private field names such as _0x5f2e and _0x4b19, inconsistent with the declared tsup build tooling. The combination of scope-level typosquat, whole-module JSFuck obfuscation, and dynamic evaluation of the obfuscated body at import time is a concealment-and-execution vehicle: whatever behavior the payload performs runs inside the installer's process without any traced-readable code path.

Malicious versions

2 flagged

1.0.41.0.7

Indicators of compromise (SHA-256)

0d3060c9289c475e223c1c00bc21a0f59f8aa5b18e31bfaee6e4d923eab0042f

3118e2d469f173e01de26e12dca51e96b8c8e2a9c0d90d1476c3472d08f82193

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 @nestjs-passport/jwt (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @nestjs-passport/jwt across your stack and pipelines.
If you installed it — respond
@nestjs-passport/jwt is a typosquat — you almost certainly intended a legitimately-named package. Remove @nestjs-passport/jwt, 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 @nestjs-passport/jwt 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 @nestjs-passport/jwt 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. @nestjs-passport/jwt on npm has been identified as a malicious package (versions 1.0.4, 1.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017136IN-MAL-2026-017135

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @nestjs-passport/jwt-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