Which versions of jwtmethod are malicious?

The following npm versions of jwtmethod are flagged malicious: 1.1.10. Treat any of these as compromised.

How do I remediate jwtmethod if I installed it?

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

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

Yes — jwtmethod is associated with the IN-MAL-2026-009604 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 jwtmethod across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for jwtmethod (version 1.1.10).

Malicious package

jwtmethodnpm

Advisory published Jul 10, 2026Updated Jul 10, 2026

jwtmethod is a confirmed malicious npm package (MAL-2026-10116) that steals credentials and exfiltrates sensitive data (malicious version 1.1.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in jwtmethod (npm)

MAL-2026-10116

Immediate action

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

npm uninstall jwtmethod

What this malware does

On module load, jwtmethod's decode.js executes a top-level routine that performs an HTTPS GET to https://jsonkeeper.com/b/E69V3 and passes the response body to new Function.constructor('require', errCode), then invokes the resulting function with the host's require. The fetched content is attacker-controlled (jsonkeeper.com is a mutable third-party paste host) and is executed with full Node capabilities, giving the attacker arbitrary code execution on the installer's machine the moment any consumer imports the package. Package metadata is forged to impersonate the auth0/jsonwebtoken ecosystem: package.json sets author: auth0 and points repository/bugs at github.com/radix-ui/primitives, and README.md is the unrelated react-text documentation from radix-ui — a lure designed to entice installers looking for a JWT library.

Malicious versions

1 flagged

1.1.10

Indicators of compromise (SHA-256)

3dbd06d83019ce10a1c0da788fc10633f55f9f6c82058ca6841c4650b5611afb

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for jwtmethod (version 1.1.10).
If you installed it — respond
jwtmethod 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 jwtmethod 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. jwtmethod on npm has been identified as a malicious package (version 1.1.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009604

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database