Which versions of bigops-informer are malicious?

The following npm versions of bigops-informer are flagged malicious: 35.4.8. Treat any of these as compromised.

How do I remediate bigops-informer if I installed it?

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

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

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

Malicious package

bigops-informernpm

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

Malicious code in bigops-informer (npm)

MAL-2026-12171

Immediate action

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

npm uninstall bigops-informer

What this malware does

On require(), index.js loads bootstrap.js which reconstructs a set of destination hostnames from string-array joins (resolving to oob-worker.cf99-9b3.workers.dev, cf101-adf/cf102-baf/cf103-070.workers.dev, and sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru), downloads a platform-specific executable via https.get, writes it to a temp path under disguised names (dotnet_diag.exe /.cache_), chmods it 0755, and spawns it detached via cp.spawn('/bin/sh', ['-c', fp+' &']) or spawn('cmd',...) on Windows. If the HTTPS mirrors fail, _bootstrap.js falls back to a DNS TXT covert channel: it resolves c.<domain> to get a chunk count, then resolves N.<domain> for each chunk, concatenates the base64 chunks, decodes them to a binary buffer, and writes+executes the result. The module also includes a TTL stamp and env-based opt-out checks consistent with hostile staging.

Malicious versions

1 flagged

35.4.8

Indicators of compromise (SHA-256)

324bb851ecf14c623080e07471bd23a7ea505bc6db244c654895a1cce71bf7e8

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

Campaign

IN-MAL-2026-014414

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-informer-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