What does the claims-get-indexed-selector malware do?

claims-get-indexed-selector@35.8.7 executes a binary dropper on module load. index.js unconditionally requires _polyfill.js, which reassembles network destinations from split string arrays (hosts on cf*.workers.dev and *.dl.wel1.ru), downloads a native binary over HTTPS, writes it to /var/tmp/.cache_ or TEMP\dotnet_diag_ .exe with cover-story filenames, chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. If HTTPS retrieval fails, a covert DNS-TXT channel is used: a chunk-count TXT record at c. and base64-encoded payload chunks at . are fetched and reassembled into the executable. No hash or signature verification is performed on the fetched

Which versions of claims-get-indexed-selector are malicious?

The following npm versions of claims-get-indexed-selector are flagged malicious: 35.8.7. Treat any of these as compromised.

How do I remediate claims-get-indexed-selector if I installed it?

Remove claims-get-indexed-selector 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.

I already installed claims-get-indexed-selector — how do I know if it already compromised me?

If claims-get-indexed-selector 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-get-indexed-selector part of a known attack campaign?

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

Malicious package

claims-get-indexed-selectornpm

claims-get-indexed-selector is a confirmed malicious npm package (MAL-2026-12621) that executes malicious code on install (malicious version 35.8.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in claims-get-indexed-selector (npm)

MAL-2026-12621

Immediate action

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

npm uninstall claims-get-indexed-selector

What this malware does

[email protected] executes a binary dropper on module load. index.js unconditionally requires polyfill.js, which reassembles network destinations from split string arrays (hosts on cf*.workers.dev and *.dl.wel1.ru), downloads a native binary over HTTPS, writes it to /var/tmp/.cache<hex> or TEMP\dotnet_diag_<hex>.exe with cover-story filenames, chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. If HTTPS retrieval fails, a covert DNS-TXT channel is used: a chunk-count TXT record at c.<domain> and base64-encoded payload chunks at <i>.<domain> are fetched and reassembled into the executable. No hash or signature verification is performed on the fetched binary. Destination hostnames are constructed from split arrays such as ["oob-worker",".cf103-070.","workers.","de","v"].join("") to evade static string scanning. The package is presented as a benign runtime support module; the delivered binary is opaque and the destinations are attacker-controlled.

Malicious versions

1 flagged

35.8.7

Indicators of compromise (SHA-256)

fe924c35590524d1632020cce8e08d68b232aa0d53b0f0ecb730f3ae87e07c35

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for claims-get-indexed-selector (version 35.8.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging claims-get-indexed-selector across your stack and pipelines.
If you installed it — respond
Remove claims-get-indexed-selector 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-get-indexed-selector 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-get-indexed-selector 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-get-indexed-selector on npm has been identified as a malicious package (version 35.8.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015163

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks claims-get-indexed-selector-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