Which versions of bigops-products-accounts-and-cards are malicious?

The following npm versions of bigops-products-accounts-and-cards are flagged malicious: 35.7.5. Treat any of these as compromised.

How do I remediate bigops-products-accounts-and-cards if I installed it?

Remove bigops-products-accounts-and-cards 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 bigops-products-accounts-and-cards — how do I know if it already compromised me?

If bigops-products-accounts-and-cards 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 bigops-products-accounts-and-cards part of a known attack campaign?

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

Malicious package

bigops-products-accounts-and-cardsnpm

bigops-products-accounts-and-cards is a confirmed malicious npm package (MAL-2026-13237) that executes malicious code on install (malicious version 35.7.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigops-products-accounts-and-cards (npm)

MAL-2026-13237

Immediate action

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

npm uninstall bigops-products-accounts-and-cards

What this malware does

On require of this package, index.js loads shim.js which selects a platform-specific binary, downloads it over HTTPS from string-split-obfuscated Cloudflare Workers hosts (oob-worker.cf101-adf.workers.dev and sibling *.workers.dev endpoints), writes it to a temp path under a disguised filename (dotnet_diag.exe /.cache_), sets it executable via chmodSync 0o755, and detached-spawns it through /bin/sh -c or cmd. A DNS TXT-record base64 channel to sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru provides a fallback delivery path. A second fully-formed dropper is shipped as lib/telemetry.js under an 'analytics SDK' cover story, implementing the same base64-assembled payload plus spawn('/bin/sh',['-c', filePath+' &']) pattern with string-concatenated API names (fs['chmod'+'Sync']). Hostnames and dangerous API identifiers are assembled at runtime via array joins to evade static analysis. Any consumer that imports the package receives arbitrary attacker-controlled code execution on their machine.

Malicious versions

1 flagged

35.7.5

Indicators of compromise (SHA-256)

dfef5ead75c58c24a4fc31b418af20b6252ac9177785002ccbf49407a28dddd8

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

Campaign

IN-MAL-2026-015753

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-products-accounts-and-cards-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