Which versions of claims-get-percentage-value are malicious?

The following npm versions of claims-get-percentage-value are flagged malicious: 35.4.6. Treat any of these as compromised.

How do I remediate claims-get-percentage-value if I installed it?

Remove claims-get-percentage-value 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-percentage-value — how do I know if it already compromised me?

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

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

Malicious package

claims-get-percentage-valuenpm

claims-get-percentage-value is a confirmed malicious npm package (MAL-2026-12622) that executes malicious code on install (malicious version 35.4.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in claims-get-percentage-value (npm)

MAL-2026-12622

Immediate action

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

npm uninstall claims-get-percentage-value

What this malware does

The package's main entry (index.js) unconditionally requires platform.js, which on module load fetches a platform-specific executable from hardcoded string-concatenated hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev), with DNS-TXT fallback to sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The fetched bytes are written to /tmp as a hidden dot-file (.cache<rand>) on Unix or to %TEMP% as dotnet_diag_<rand>.exe on Windows, chmod 0755'd, and spawned detached via /bin/sh -c or cmd.exe start /b. Endpoint hosts and dropped file names are assembled from split string fragments; the dotnet_diag /.cache / analytics_state names and DISABLE_TELEMETRY / DO_NOT_TRACK env-var checks form a telemetry cover story unrelated to the package's advertised purpose (a trivial percentage-value class). No hash or signature verification is performed on the downloaded binary.

Malicious versions

1 flagged

35.4.6

Indicators of compromise (SHA-256)

fcb53d2b24eba1d763f7d76c41b006cc7a6d236677fcc2749b310cb3389ab161

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-percentage-value (version 35.4.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging claims-get-percentage-value across your stack and pipelines.
If you installed it — respond
Remove claims-get-percentage-value 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-percentage-value 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-percentage-value 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-percentage-value on npm has been identified as a malicious package (version 35.4.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015162

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks claims-get-percentage-value-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