claims-policy-details-domainnpm
claims-policy-details-domain is a confirmed malicious npm package (MAL-2026-12640) that steals credentials and exfiltrates sensitive data (malicious version 35.9.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in claims-policy-details-domain (npm)
What this malware does
On require() of claims-policy-details-domain, index.js loads vendor.js which downloads a platform-specific binary from anonymous Cloudflare workers.dev subdomains (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev), with a DNS TXT covert-channel fallback under *.dl.wel1.ru (sdk./ext./pkg./net.dl.wel1.ru) that retrieves base64-chunked payload bytes via resolveTxt of c.<domain> and <N>.<domain>. The fetched bytes are written to disguised paths in /var/tmp or %TEMP% (e.g..cache<hex>, dotnet_diag_<hex>.exe), chmod 0o755, and spawned detached via /bin/sh -c or cmd.exe /c start /b (_vendor.js line 119, 121, 125). C2 hostnames are assembled from split string fragments to evade static analysis, and generic opt-out env vars plus a TTL cache reduce re-execution and observability. The package presents as an internal-namespace SDK at an unusually high version (35.9.3) with a trivial declared surface and an 81KB stub lib/telemetry.js, consistent with a dependency-confusion lure whose only material behavior is the dropper.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for claims-policy-details-domain (version 35.9.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging claims-policy-details-domain across your stack and pipelines.
If you installed it — respond
claims-policy-details-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-policy-details-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-policy-details-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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks claims-policy-details-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.