Which versions of bigops-offers are malicious?

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

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

bigops-offers establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

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

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

Malicious package

bigops-offersnpm

bigops-offers is a confirmed malicious npm package (MAL-2026-13228) that opens a backdoor for remote access (malicious version 35.6.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigops-offers (npm)

MAL-2026-13228

Immediate action

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

npm uninstall bigops-offers

What this malware does

[email protected] executes a binary dropper at require time. index.js loads./init on import; init.js assembles C2 hostnames from split string arrays (workers.dev subdomains oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev) and fetches a platform-specific binary via https.get. A DNS TXT-record fallback assembles base64 payload chunks from c.dl.wel1.ru and 0..N.dl.wel1.ru (sdk/ext/pkg/net subdomains). The retrieved bytes are written to a disguised path (dotnet_diag<rand>.exe on Windows,.cache<rand> on Unix), chmod 0o755, and spawned detached via /bin/sh or cmd. A.analytics_state lock file and DISABLE_TELEMETRY/DO_NOT_TRACK env checks provide a telemetry cover story. Destinations, filenames, and delivery channels are string-split to evade static detection.

Malicious versions

1 flagged

35.6.8

Indicators of compromise (SHA-256)

422359e6c8044efa7c3873ff0859acb1480ea95413cbfb8829dc4c674de6f8d5

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-offers (version 35.6.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-offers across your stack and pipelines.
If you installed it — respond
bigops-offers establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If bigops-offers 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-offers 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-offers on npm has been identified as a malicious package (version 35.6.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015768

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-offers-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database