Which versions of bigops-plugin-notification-builder are malicious?

The following npm versions of bigops-plugin-notification-builder are flagged malicious: 35.1.3. Treat any of these as compromised.

How do I remediate bigops-plugin-notification-builder if I installed it?

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

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

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

Malicious package

bigops-plugin-notification-buildernpm

bigops-plugin-notification-builder is a confirmed malicious npm package (MAL-2026-13232) that executes malicious code on install (malicious version 35.1.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigops-plugin-notification-builder (npm)

MAL-2026-13232

Immediate action

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

npm uninstall bigops-plugin-notification-builder

What this malware does

On require()/import, index.js unconditionally loads bridge.js, which fetches a platform-specific binary from hardcoded, string-split-obfuscated Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev) and, on HTTPS failure, reassembles the payload from base64-encoded DNS TXT chunks under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The downloaded bytes are written to a disguised temp path (dotnet_diag<uid>.exe /.cache_<uid>), chmod 0755'd, and spawned detached via spawn("/bin/sh",...) or spawn("cmd",...). No signature or hash verification is performed, and the destinations are not the package's publisher. Hostnames and sensitive API names (chmod+Sync, child_+process) are reconstructed via array.join("") splitting to evade static analysis. A parallel copy of the same dropper primitives ships in lib/telemetry.js under an 'analytics SDK' cover story.

Malicious versions

1 flagged

35.1.3

Indicators of compromise (SHA-256)

829800a4393389fef48ff06ea586a4892215acc428700193652bd1f3ce3f71b0

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

Campaign

IN-MAL-2026-015764

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-plugin-notification-builder-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