CRITICAL npm Malware

Malicious code in bigops-umf-statist (npm)

MAL-2026-12852 · GHSA-65hm-c5q4-xqrc

Published · Modified

Dependency scanning

Check whether bigops-umf-statist is in your codebase

Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.

Description


__

Source: amazon-inspector (da63079fe1017b1a4ade225e41fbb7479ab0a247b235d62b252470ff9f07e1d7)

On require('bigops-umf-statist'), index.js loads runtime.js which selects a platform-specific endpoint, downloads a binary over HTTPS from string-obfuscated Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT fallback channel that reassembles a base64 payload from TXT records under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched bytes are written to /var/tmp or %TEMP% under a masquerading name (dotnet_diag.exe or.cache_), chmod 0755, and spawned detached via cmd.exe or /bin/sh. Destination hostnames are reconstructed at runtime by array-join to evade static inspection, and no signature or hash verification is performed on the downloaded payload.

Source: ghsa-malware (3bb2495d4e155a4b2f24971c9596f31877b30315ca6b62afd1c9347505d5e433)

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Ready to move

Start Securing

Free, no credit card | First findings in minutes