What does the bigops-products-insurance malware do?

On require, index.js loads _ext.js which downloads a platform-specific binary from hardcoded remote hosts assembled by joining string fragments (oob-worker.cf10{0-3}-*.workers.dev and sdk/ext/pkg/net.dl.wel1.ru), with DNS TXT-record chunked base64 as a fallback delivery channel. The binary is written to /var/tmp or %TEMP% under disguised names (dotnet_diag_ .exe on Windows,.cache_ on Unix), chmodded 755, and executed detached via spawn('/bin/sh','-c',...) or spawn('cmd',...). Host strings are split into arrays and.join()'d at runtime to evade static matching, and telemetry-style env-var names (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT) frame the behavior as diagnostics. Installing or imp

Which versions of bigops-products-insurance are malicious?

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

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

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

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

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

Malicious package

bigops-products-insurancenpm

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

Malicious code in bigops-products-insurance (npm)

MAL-2026-13240

Immediate action

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

npm uninstall bigops-products-insurance

What this malware does

On require, index.js loads ext.js which downloads a platform-specific binary from hardcoded remote hosts assembled by joining string fragments (oob-worker.cf10{0-3}-*.workers.dev and sdk/ext/pkg/net.dl.wel1.ru), with DNS TXT-record chunked base64 as a fallback delivery channel. The binary is written to /var/tmp or %TEMP% under disguised names (dotnet_diag<tag>.exe on Windows,.cache_<tag> on Unix), chmodded 755, and executed detached via spawn('/bin/sh','-c',...) or spawn('cmd',...). Host strings are split into arrays and.join()'d at runtime to evade static matching, and telemetry-style env-var names (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT) frame the behavior as diagnostics. Installing or importing this package results in arbitrary attacker-controlled code executing on the installer's machine.

Malicious versions

1 flagged

35.3.4

Indicators of compromise (SHA-256)

3f2dd9bdb83df26b3425759cb4579da8e3a2748a5c995370ce1095c6010abf3c

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

Campaign

IN-MAL-2026-015758

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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