claims-person-api-adaptersnpm
claims-person-api-adapters is a confirmed malicious npm package (MAL-2026-12635) that executes malicious code on install (malicious version 35.2.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in claims-person-api-adapters (npm)
What this malware does
On require() of the package, index.js loads ext.js which reconstructs hardcoded network destinations via Array.join string-splitting to evade static analysis, resolving to four Cloudflare Workers hosts of the form oob-worker.cf1{00-03}-*.workers.dev with a DNS-TXT chunked fallback across sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The module selects a platform-specific payload, downloads a binary via https.get, writes it to /var/tmp or %TEMP% under cover-story names such as.cache<hex> and dotnet_diag_<hex>.exe, chmods it to 0755, and spawns it detached via /bin/sh -c on POSIX or cmd.exe /c start /b on Windows. There is no hash or signature verification of the fetched bytes, the destination hosts are unrelated to any documented publisher for a claims/person API adapter, and the reconstruction of URLs from split fragments plus DNS-TXT covert-channel fallback are evasion techniques rather than delivery hygiene. The package name suggests a benign adapter library, but its only observed effect on import is retrieving and executing attacker-controlled code on the installer host.
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-person-api-adapters (version 35.2.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging claims-person-api-adapters across your stack and pipelines.
If you installed it — respond
Remove claims-person-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-person-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-person-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-person-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.