What does the claims-historical-claims-domain malware do?

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_ .exe on Windows,.cache_ 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 nam

Which versions of claims-historical-claims-domain are malicious?

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

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

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.

I already installed claims-historical-claims-domain — how do I know if it already compromised me?

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

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

Malicious package

claims-historical-claims-domainnpm

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

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for claims-historical-claims-domain (version 35.4.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging claims-historical-claims-domain across your stack and pipelines.
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.
Did it already run?
If claims-historical-claims-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-historical-claims-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-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

npmjs.com

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