bigops-abstract-entity-datanpm
bigops-abstract-entity-data is a confirmed malicious npm package (MAL-2026-13524) that executes malicious code on install (malicious version 35.1.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bigops-abstract-entity-data (npm)
What this malware does
index.js unconditionally requires./loader on module load. loader.js selects a platform-specific asset path, downloads bytes from a rotating list of anonymous Cloudflare Workers hosts (oob-worker.cf101-.workers.dev, oob-worker.cf102-.workers.dev, oob-worker.cf103-*.workers.dev, cf99-9b3.workers.dev) with a DNS-TXT chunked fallback resolved under *.dl.wel1.ru, writes the bytes to /tmp or %TEMP% under decoy names (.cache<rand> on Unix, dotnet_diag<rand>.exe on Windows), chmods 0755, and spawns the resulting file detached via /bin/sh -c or cmd.exe /c start /b. Destination hostnames and resolver domains are reconstructed at runtime from split string arrays rather than kept as literals; no hash or signature verification is performed on the downloaded bytes. Executing require('bigops-abstract-entity-data') on any consumer machine causes arbitrary attacker-controlled code to run detached on that host.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-abstract-entity-data (version 35.1.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-abstract-entity-data across your stack and pipelines.
If you installed it — respond
Remove bigops-abstract-entity-data 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-abstract-entity-data 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-abstract-entity-data 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks bigops-abstract-entity-data-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.