Which versions of bigops-customer-processing-client are malicious?

The following npm versions of bigops-customer-processing-client are flagged malicious: 35.1.8. Treat any of these as compromised.

How do I remediate bigops-customer-processing-client if I installed it?

bigops-customer-processing-client establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed bigops-customer-processing-client — how do I know if it already compromised me?

If bigops-customer-processing-client 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-customer-processing-client part of a known attack campaign?

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

Malicious package

bigops-customer-processing-clientnpm

bigops-customer-processing-client is a confirmed malicious npm package (MAL-2026-12162) that opens a backdoor for remote access (malicious version 35.1.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigops-customer-processing-client (npm)

MAL-2026-12162

Immediate action

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

npm uninstall bigops-customer-processing-client

What this malware does

On require() of this package, index.js loads support.js which unconditionally invokes setup(). setup() assembles C2 hostnames via.join('') from fragmented substrings, resolving to *.workers.dev endpoints (oob-worker.cf100-416.workers.dev, cf101-adf.workers.dev, cf102-baf.workers.dev) with a DNS-TXT fallback under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. A platform-specific binary is fetched over HTTPS, written to /tmp or %TEMP% under disguised filenames (dotnet_diag<rand>.exe,.cache_<rand>), chmod 0755, and detach-spawned via cmd /c start /b or /bin/sh -c. No hash or signature verification is performed despite a comment claiming a SHA-256 check. Hostname fragmentation, cover-story comments, and disguised drop paths indicate deliberate evasion.

Malicious versions

1 flagged

35.1.8

Indicators of compromise (SHA-256)

f9d2fe146d4919092aae053b82b0caacff3789c10e63358f880fa5ab4590b3d2

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-customer-processing-client (version 35.1.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-customer-processing-client across your stack and pipelines.
If you installed it — respond
bigops-customer-processing-client establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If bigops-customer-processing-client 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-customer-processing-client 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-customer-processing-client on npm has been identified as a malicious package (version 35.1.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014415

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-customer-processing-client-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database