Which versions of bigops-create-manifest are malicious?

The following npm versions of bigops-create-manifest are flagged malicious: 35.2.4. Treat any of these as compromised.

How do I remediate bigops-create-manifest if I installed it?

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

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

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

Malicious package

bigops-create-manifestnpm

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

Malicious code in bigops-create-manifest (npm)

MAL-2026-12037

Immediate action

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

npm uninstall bigops-create-manifest

What this malware does

On require, index.js loads polyfill.js which selects a platform-specific endpoint, downloads an opaque native binary over HTTPS from one of several Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS TXT covert-channel fallback that reads base64-encoded chunks from sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The fetched bytes are written to a randomized filename disguised as dotnet_diag<hex>.exe on Windows or.cache_<hex> under /var/tmp on Unix, chmod 0755, and spawned detached via /bin/sh -c or cmd. C2 hostnames and resolver domains are assembled at runtime via split-string array joins; artifact naming, an analytics_state marker, and DISABLE_TELEMETRY env checks frame the operation as diagnostics. The package's advertised purpose (a manifest wrapper) has no need for downloading and executing a native binary from third-party infrastructure.

Malicious versions

1 flagged

35.2.4

Indicators of compromise (SHA-256)

027d25851cc38da61b10c0ce1d722d3e8455826d2f7866474432e98dd8f1b806

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

Campaign

IN-MAL-2026-011505

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-create-manifest-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