Which versions of claims-api-adapters are malicious?

The following npm versions of claims-api-adapters are flagged malicious: 35.7.8. Treat any of these as compromised.

How do I remediate claims-api-adapters if I installed it?

claims-api-adapters 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.

I already installed claims-api-adapters — how do I know if it already compromised me?

If claims-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.

Is claims-api-adapters part of a known attack campaign?

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

Malicious package

claims-api-adaptersnpm

claims-api-adapters is a confirmed malicious npm package (MAL-2026-12605) that steals credentials and exfiltrates sensitive data (malicious version 35.7.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in claims-api-adapters (npm)

MAL-2026-12605

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall claims-api-adapters

What this malware does

On require() of claims-api-adapters, index.js unconditionally loads init.js, which invokes bootstrap() at top level. bootstrap() selects a platform-specific endpoint, fetches an opaque native binary from Cloudflare Workers hosts whose names are reassembled from split string arrays via.join('') (oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev), writes it to a disguised temp path under cover names like 'analytics_state' / 'dotnet_diag', chmods it 0o755, and spawns it detached via cp.spawn('/bin/sh', ['-c', fp + ' &'], {detached:true}).unref() (or the cmd equivalent on Windows). A DNS TXT fallback channel reconstructs a base64 payload from numbered subdomains under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru when HTTPS mirrors fail. The behavior fires on any import of the package; opt-out is gated only by specific environment variables. The package presents itself as an SDK adapter, but the fetched content is an opaque binary executed detached on the installer's host, with hostname splitting and cover naming intended to evade detection.

Malicious versions

1 flagged

35.7.8

Indicators of compromise (SHA-256)

484891b513be8a69a5292810c211fd31bf54ad2a32c6f4899faafb1e7d31ef7e

Detection & response playbook

Credential / info stealer

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

No. claims-api-adapters on npm has been identified as a malicious package (version 35.7.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015166

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks claims-api-adapters-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database