Which versions of claims-fixtures-shared are malicious?

The following npm versions of claims-fixtures-shared are flagged malicious: 35.8.6. Treat any of these as compromised.

How do I remediate claims-fixtures-shared if I installed it?

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

If claims-fixtures-shared was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is claims-fixtures-shared part of a known attack campaign?

Yes — claims-fixtures-shared is associated with the IN-MAL-2026-015160 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-fixtures-shared across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for claims-fixtures-shared (version 35.8.6).

Malicious package

claims-fixtures-sharednpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

claims-fixtures-shared is a confirmed malicious npm package (MAL-2026-12615) that executes malicious code on install (malicious version 35.8.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in claims-fixtures-shared (npm)

MAL-2026-12615

Immediate action

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

npm uninstall claims-fixtures-shared

What this malware does

On require('claims-fixtures-shared'), index.js loads helpers.js which immediately calls init(). init() reconstructs four Cloudflare Workers hostnames (oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev) and a set of DNS TXT-record resolvers (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru) via runtime array.join("") to evade static string scanners, then downloads a per-platform binary via https.get, writes it to /tmp or %TEMP% under a masquerading filename (.cache<rnd> on unix, dotnet_diag_<rnd>.exe on Windows), fs.chmodSync 0o755, and spawns it detached via /bin/sh -c or cmd. No signature or hash verification is performed despite a '// SHA-256 integrity check' cover-story comment; a DNS TXT-record fallback channel and a.analytics_state lock file for rerun throttling are present. The package's stated purpose is a trivial fixtures helper, unrelated to any native binary. Env-var opt-outs (DISABLE_TELEMETRY, DO_NOT_TRACK) frame the code as telemetry while it stages and executes an arbitrary attacker-controlled payload.

Malicious versions

1 flagged

35.8.6

Indicators of compromise (SHA-256)

291919ef20015ad326b92c506f2df9e710e72e659499bfd240c9b6453bf0fd82

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for claims-fixtures-shared (version 35.8.6).
If you installed it — respond
Remove claims-fixtures-shared 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-fixtures-shared was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-015160

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks claims-fixtures-shared-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