Which versions of claims-get-base-url are malicious?

The following npm versions of claims-get-base-url are flagged malicious: 35.4.5. Treat any of these as compromised.

How do I remediate claims-get-base-url if I installed it?

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

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

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

Malicious package

claims-get-base-urlnpm

claims-get-base-url is a confirmed malicious npm package (MAL-2026-12619) that executes malicious code on install (malicious version 35.4.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in claims-get-base-url (npm)

MAL-2026-12619

Immediate action

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

npm uninstall claims-get-base-url

What this malware does

index.js requires./setup on load, so any require() of this package triggers a dropper chain. setup.js selects a platform-specific payload path (linux/darwin/win32), downloads a binary over HTTPS from string-split-obfuscated hosts of the form oob-worker.cf10X-*.workers.dev with a DNS TXT-record fallback channel under sdk.dl.wel1.ru (hostnames are assembled at runtime via array joins such as ["oob-worker.cf102-baf.workers.de","v"].join("") to hide the.dev TLD from static scanners), writes it to a hidden path under /var/tmp or %TEMP% (.cache_<hex> / dotnet_diag_<hex>.exe), chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe with stdio ignored and unref()'d. lib/telemetry.js contains a second, dormant copy of the same dropper shape (base64 chunk assembly, chmod 0755, detached /bin/sh spawn), referencing child_process as 'child_'+'process'. The package's advertised purpose ("claims get base url interface") has no legitimate need for cross-platform binary fetch-and-execute; the obfuscation, DNS fallback channel, and hidden dotfile staging are canonical import-time dropper tradecraft. Installing and loading this package runs attacker-controlled native code on the installer's machine.

Malicious versions

1 flagged

35.4.5

Indicators of compromise (SHA-256)

7e7b7dbbb58284ead0ecb4d93490e9683b4f58b31955d817de52495fb7399106

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

Campaign

IN-MAL-2026-015157

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks claims-get-base-url-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