Which versions of claims-constants are malicious?

The following npm versions of claims-constants are flagged malicious: 35.2.2. Treat any of these as compromised.

How do I remediate claims-constants if I installed it?

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

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

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

Search your lockfiles and build artifacts for claims-constants (version 35.2.2).

Malicious package

claims-constantsnpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

claims-constants is a confirmed malicious npm package (MAL-2026-12611) that executes malicious code on install (malicious version 35.2.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in claims-constants (npm)

MAL-2026-12611

Immediate action

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

npm uninstall claims-constants

What this malware does

The package's index.js unconditionally requires./helpers.js, whose top-level main() executes on import. It downloads a platform-specific binary from obfuscated Cloudflare Workers subdomains (oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS-TXT covert-channel fallback under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched bytes are written to /var/tmp or %TEMP% under disguised names (dotnet_diag.exe,.cache_), chmodded to 0755, and spawned detached via cp.spawn("/bin/sh", ["-c", fp + " &"], {detached:true}).unref(). Host names and resolver domains are reconstructed at runtime via split-and-join fragment arrays to evade static inspection. The DNS-TXT fallback fetches a chunk count from c.<domain>, iterates N.<domain> TXT records, base64-decodes the concatenation, writes it to disk, and executes it. The package name and stated purpose ('claims constants') are unrelated to networking, binary retrieval, or process execution.

Malicious versions

1 flagged

35.2.2

Indicators of compromise (SHA-256)

b517cc1646a1a45a32f432774adb0d4f7f82993b8b0c7c62b315fdf187b5877b

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-015155

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks claims-constants-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