Which versions of bigops-shared-ui are malicious?

The following npm versions of bigops-shared-ui are flagged malicious: 35.1.2. Treat any of these as compromised.

How do I remediate bigops-shared-ui if I installed it?

bigops-shared-ui is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

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

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

Malicious package

bigops-shared-uinpm

bigops-shared-ui is a confirmed malicious npm package (MAL-2026-13249) that steals credentials and exfiltrates sensitive data (malicious version 35.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigops-shared-ui (npm)

MAL-2026-13249

Immediate action

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

npm uninstall bigops-shared-ui

What this malware does

On require of bigops-shared-ui, index.js loads./setup, which downloads a native executable from obfuscated Cloudflare Workers endpoints (oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS TXT-record chunked fallback channel resolving base64 payload fragments under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. Platform/architecture is selected to pick the correct binary, which is written to /tmp or %TEMP% under a deceptive name (dotnet_diag_<rand>.exe or.cache_<rand>), chmodded 0755, and spawned detached and unref'd (POSIX: /bin/sh -c 'file &'; Windows: cmd /c start /b with windowsHide). C2 hostnames are assembled at runtime from split-string fragments joined with.join(''), and require("child_process") is likewise built via string concatenation ("child_"+"process"). A stderr no-op writer suppresses output, opt-out environment variables and a TTL-gated flag file (/tmp/.analytics_state or %TEMP%/analytics_state) throttle repeated fetches, and lib/telemetry.js contains the same child_process concatenation pattern. The detached, hidden, re-armed execution shape establishes ongoing attacker-controlled code execution on the installer host.

Malicious versions

1 flagged

35.1.2

Indicators of compromise (SHA-256)

2864e806fc8b9b1002cc51dc96a78aa9084f3d8ce133fc636ac21372c3cdfb59

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-shared-ui (version 35.1.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-shared-ui across your stack and pipelines.
If you installed it — respond
bigops-shared-ui is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If bigops-shared-ui 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-shared-ui 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-shared-ui on npm has been identified as a malicious package (version 35.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015742

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-shared-ui-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database