NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

claims-historical-claims-domainnpm

Advisory published Updated

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

Malicious code in claims-historical-claims-domain (npm)

MAL-2026-12625
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall claims-historical-claims-domain

What this malware does

On require, index.js loads bridge.js which selects a platform-specific URL path and downloads a binary via https.get from hostnames assembled by string-splitting fragments such as 'oob-worker.cf*-.workers.dev', with a DNS TXT-record base64 fallback under '.dl.wel1.ru'. The fetched bytes are written to a temp file under a masquerading name (dotnet_diag<rnd>.exe on Windows,.cache_<rnd> on Unix), chmodded 0755, and spawned detached via /bin/sh -c or cmd. No hash or signature verification is performed. A freshness marker file named 'analytics_state' gates re-runs to roughly once per six hours, and code comments frame the behavior as 'telemetry'/'analytics'. Host destinations and artifact names are obfuscated via array-join string splitting to defeat literal-string scanning.

Malicious versions

1 flagged
35.4.4

Indicators of compromise (SHA-256)

821551bfee1b6a8fa74b001808fad75327d22654f228600f02a6130edc31ce2e

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for claims-historical-claims-domain (version 35.4.4).

  2. If you installed it — respond

    Remove claims-historical-claims-domain 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.

  3. Did it already run?

    If claims-historical-claims-domain 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-historical-claims-domain on npm has been identified as a malicious package (version 35.4.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015145

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks claims-historical-claims-domain-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
claims-historical-claims-domain (npm) malicious package — MAL-2026-12625 | O3 Security