What does the bigops-products-deposits malware do?

On require of this package, index.js loads _runtime.js which auto-invokes an init routine that selects a platform-specific endpoint, downloads a binary over HTTPS from hostnames reconstructed via string-array joins (e.g. oob-worker.cf101-adf.workers.dev and sdk.dl.wel1.ru), with a DNS TXT chunked-base64 fallback channel (count read from c. , payload chunks from . ). The fetched bytes are written to /tmp or %TEMP% under names impersonating system diagnostics (.cache_ , dotnet_diag_ .exe), chmod 0755, and spawned detached via /bin/sh -c or cmd with unref(), yielding remote code execution on the installer host. A state file.analytics_state is used to masquerade as telem

Which versions of bigops-products-deposits are malicious?

The following npm versions of bigops-products-deposits are flagged malicious: 35.9.1. Treat any of these as compromised.

How do I remediate bigops-products-deposits if I installed it?

bigops-products-deposits is a typosquat — you almost certainly intended a legitimately-named package. Remove bigops-products-deposits, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed bigops-products-deposits — how do I know if it already compromised me?

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

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

Malicious package

bigops-products-depositsnpm

bigops-products-deposits is a confirmed malicious npm package (MAL-2026-13239) that typosquats a legitimate package to trick installs (malicious version 35.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigops-products-deposits (npm)

MAL-2026-13239

Immediate action

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

npm uninstall bigops-products-deposits

What this malware does

On require of this package, index.js loads runtime.js which auto-invokes an init routine that selects a platform-specific endpoint, downloads a binary over HTTPS from hostnames reconstructed via string-array joins (e.g. oob-worker.cf101-adf.workers.dev and sdk.dl.wel1.ru), with a DNS TXT chunked-base64 fallback channel (count read from c.<domain>, payload chunks from <i>.<domain>). The fetched bytes are written to /tmp or %TEMP% under names impersonating system diagnostics (.cache<hex>, dotnet_diag_<hex>.exe), chmod 0755, and spawned detached via /bin/sh -c or cmd with unref(), yielding remote code execution on the installer host. A state file.analytics_state is used to masquerade as telemetry.

Malicious versions

1 flagged

35.9.1

Indicators of compromise (SHA-256)

a5f53755fd64cd249daeb83c1f148b5f4e600e4f59cc07cfa99fe6579992b0a9

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-products-deposits (version 35.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-products-deposits across your stack and pipelines.
If you installed it — respond
bigops-products-deposits is a typosquat — you almost certainly intended a legitimately-named package. Remove bigops-products-deposits, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If bigops-products-deposits 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-deposits 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-deposits on npm has been identified as a malicious package (version 35.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015759

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-products-deposits-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