claims-policies-api-adaptersnpm
claims-policies-api-adapters is a confirmed malicious npm package (MAL-2026-12637) that executes malicious code on install (malicious version 35.6.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in claims-policies-api-adapters (npm)
What this malware does
On require() of claims-policies-api-adapters, index.js loads vendor.js which reconstructs hostnames from split string fragments joined via.join(''), fetches a platform-specific binary over HTTPS from hardcoded Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev), with DNS TXT records under *.dl.wel1.ru as a covert fallback channel that base64-assembles the payload. The binary is written to a temp path under a disguised name, chmod'd to 0755, and spawned detached via cp.spawn('/bin/sh', ['-c', path + ' &'], {detached:true}) on Unix or cmd.exe start /b on Windows. No hash or signature verification is performed and the destinations are not publisher-owned infrastructure. An opt-out env-var gate and a '.analytics_state' freshness marker suppress re-execution. A second module lib/telemetry.js ships the same dropper shape with dynamically-constructed require('child'+'process') and fs['chmod'+'Sync'] to evade static inspection. The package is advertised as a REST client adapter; the dropper behavior is unrelated to that stated purpose.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for claims-policies-api-adapters (version 35.6.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging claims-policies-api-adapters across your stack and pipelines.
If you installed it — respond
Remove claims-policies-api-adapters 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-policies-api-adapters 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-policies-api-adapters 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-policies-api-adapters-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.