Which versions of claims-auth-domain are malicious?

The following npm versions of claims-auth-domain are flagged malicious: 35.5.4. Treat any of these as compromised.

How do I remediate claims-auth-domain if I installed it?

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

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

Yes — claims-auth-domain is associated with the IN-MAL-2026-015167 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-auth-domain 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 claims-auth-domain (version 35.5.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging claims-auth-domain across your stack and pipelines.

Malicious package

claims-auth-domainnpm

claims-auth-domain is a confirmed malicious npm package (MAL-2026-12608) that steals credentials and exfiltrates sensitive data (malicious version 35.5.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in claims-auth-domain (npm)

MAL-2026-12608

Immediate action

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

npm uninstall claims-auth-domain

What this malware does

On require('claims-auth-domain'), index.js loads vendor.js which selects a platform-specific endpoint, downloads a binary from hardcoded attacker infrastructure, stages it under /tmp or %TEMP% with a disguised name ('.cache<hex>' on Unix, 'dotnet_diag_<hex>.exe' on Windows), sets it executable via chmod 0755, and spawns it detached via /bin/sh or cmd. Destination hostnames are assembled by concatenating split string fragments (e.g. ['oob-worker.cf101-ad','f.work','ers','.d','ev'].join('')) to hide the C2 domains from static inspection. If HTTPS delivery from *.workers.dev fails, _vendor.js falls back to reassembling the payload from chunked DNS TXT records under *.dl.wel1.ru: a count is fetched from c.<domain>, then N.<domain> TXT chunks are base64-decoded and concatenated into the executable. Cover-story framing labels the code as telemetry/analytics and honors DISABLE_TELEMETRY / DO_NOT_TRACK env vars to reduce detection. The result on any host that installs and loads this package is import-time full-host code execution under attacker control.

Malicious versions

1 flagged

35.5.4

Indicators of compromise (SHA-256)

689620689df62b0e31d3caeb29327b88da40bae2bb66da3075dde6ee311ea6c3

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for claims-auth-domain (version 35.5.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging claims-auth-domain across your stack and pipelines.
If you installed it — respond
claims-auth-domain 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 claims-auth-domain 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 claims-auth-domain 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. claims-auth-domain on npm has been identified as a malicious package (version 35.5.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015167

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks claims-auth-domain-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