Which versions of claims-person-domain are malicious?

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

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

claims-person-domain is a typosquat — you almost certainly intended a legitimately-named package. Remove claims-person-domain, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

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

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

Malicious package

claims-person-domainnpm

claims-person-domain is a confirmed malicious npm package (MAL-2026-12636) that typosquats a legitimate package to trick installs (malicious version 35.5.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in claims-person-domain (npm)

MAL-2026-12636

Immediate action

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

npm uninstall claims-person-domain

What this malware does

On require of the package's main entry, index.js loads./support.js which selects a platform-specific asset path (linux/darwin/win32), fetches an opaque binary from one of four Cloudflare Workers endpoints whose hostnames are assembled at runtime by joining fragmented string arrays (oob-worker.cf{99-9b3,101-adf,102-baf,103-070}.workers.dev), with a DNS-TXT covert-channel fallback via {sdk,ext,pkg,net}.dl.wel1.ru. The fetched bytes are written to /var/tmp or %TEMP% under disguised names (.cache<hex>, dotnet_diag_<hex>.exe), chmod'd 0755, and spawned detached via /bin/sh -c or cmd.exe. A persistence marker at /tmp/.analytics_state prevents re-execution. A parallel dropper implementation is bundled in lib/telemetry.js (self-labeled 'Analytics SDK', 81KB) that base64-decodes a payload buffer and spawns it the same way; both files use runtime string concatenation (require("child_" + "process"), fs["chmod" + "Sync"]) to evade static analysis. The obfuscation, disguised filenames mimicking diagnostic tooling, DNS-TXT fallback, and dual dropper implementations have no legitimate purpose.

Malicious versions

1 flagged

35.5.9

Indicators of compromise (SHA-256)

03f8408e0f3ee2e4d802003cc54666a1e535bbd512e8515d1ef3b7a63acf16d8

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for claims-person-domain (version 35.5.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging claims-person-domain across your stack and pipelines.
If you installed it — respond
claims-person-domain is a typosquat — you almost certainly intended a legitimately-named package. Remove claims-person-domain, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If claims-person-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-person-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-person-domain on npm has been identified as a malicious package (version 35.5.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015131

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks claims-person-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