Which versions of claimora are malicious?

The following npm versions of claimora are flagged malicious: 1.0.4. Treat any of these as compromised.

How do I remediate claimora if I installed it?

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

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

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

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

Search your lockfiles and build artifacts for claimora (version 1.0.4).

Malicious package

claimoranpm

Advisory published Jun 11, 2026Updated Jun 11, 2026

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

Malicious code in claimora (npm)

MAL-2026-5608

Immediate action

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

npm uninstall claimora

What this malware does

claimora impersonates the jsonwebtoken library (auth0): package.json sets author to "auth0", points repository at a non-existent github.com/auth0/node-claimora, and re-exports the jsonwebtoken API surface (sign/verify/decode plus JsonWebTokenError/NotBeforeError/TokenExpiredError). README and LICENSE text are copied from node-jsonwebtoken. The main entry index.js loads decode.js, which at module top level invokes getThirdCookie() — this issues an axios GET to https://jsonkeeper.com/b/0GXBD, takes response.data.errCode (attacker-controlled JavaScript on a mutable public paste service), constructs new Function.constructor("require", errCode), and invokes the resulting handler with require. Any process that requires claimora executes whatever code the operator of that paste currently serves, with full Node module access (filesystem, network, child_process, env). The legitimate jsonwebtoken library performs zero network I/O; this clone adds a remote-fetch-and-eval path executed unconditionally on import.

Malicious versions

1 flagged

1.0.4

Indicators of compromise (SHA-256)

1b785b842f24aeae0e20157784b17a8bff7003e72575ac9a3aa9cbeb550a5c92

5072f0c8720be41c60a0246459f7cde79dd300af7aa0b04e7223836a99c201a7

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for claimora (version 1.0.4).
If you installed it — respond
claimora is a typosquat — you almost certainly intended a legitimately-named package. Remove claimora, 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 claimora 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. claimora on npm has been identified as a malicious package (version 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005704IN-MAL-2026-005705

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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