Which versions of bigops-notes are malicious?

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

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

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

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

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

Malicious package

bigops-notesnpm

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

Malicious code in bigops-notes (npm)

MAL-2026-13227

Immediate action

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

npm uninstall bigops-notes

What this malware does

On require() of bigops-notes, bootstrap.js selects a platform-specific asset, downloads an opaque binary from one of four runtime-assembled *.workers.dev hostnames (oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev), with a DNS-TXT base64 fallback to *.dl.wel1.ru (sdk/ext/pkg/net). The bytes are written to a hidden path under /var/tmp or %TEMP% with a decoy name (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmod 0755, and spawned detached via /bin/sh -c or cmd. Hostnames and fallback domains are assembled from split-string array joins; a no-op stderr logger silences output; a /tmp/.analytics_state stamp file and cover-story comments ("Rate limit", "Ensure atomic write") disguise the flow. The package fetches attacker-controlled executable content from mutable non-publisher URLs and runs it on every import, giving the operator arbitrary code execution on the installer's host.

Malicious versions

1 flagged

35.8.7

Indicators of compromise (SHA-256)

51b318f6ad8ba92430c504fd94111609cc003a62f8bce36e3c1f41308b195dae

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

Campaign

IN-MAL-2026-015773

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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