Malicious code in bigops-operator-status (npm)
The bigops-operator-status npm package version 35.4.5 contains malicious code that, upon being required, downloads and executes a platform-specific binary payload from obfuscated Cloudflare Workers hostnames or, if that fails, via a DNS-TXT covert channel. This payload is written to temporary directories, made executable, and run detached, enabling remote code execution. The payload sources are not controlled by the package publisher, and the binary content is opaque, indicating a fully functional remote code execution dropper triggered at module load.
AI Analysis
Technical Summary
The bigops-operator-status npm package version 35.4.5 includes malicious functionality in its _support.js module. When the package is loaded, it dynamically constructs obfuscated Cloudflare Workers hostnames to fetch a binary payload specific to the host platform (Linux, Darwin, Windows). This payload is saved to a disguised path in the system's temporary directory, permissions are set to executable, and it is executed detached from the main process. If the HTTPS fetch fails, the module falls back to retrieving the payload through a DNS-TXT record covert channel from multiple domains. The payload sources are external and not controlled by the package publisher, and the binary payload is opaque, making this a remote code execution dropper activated immediately upon module load.
Potential Impact
This malicious package enables remote code execution on any system that loads the affected version 35.4.5 of bigops-operator-status. The attacker can execute arbitrary binaries on the victim system with the privileges of the running process, potentially leading to full system compromise. The obfuscation and fallback mechanisms increase the difficulty of detection and mitigation.
Mitigation Recommendations
No official patch or remediation is currently documented for this malicious package version. Users should immediately remove version 35.4.5 of bigops-operator-status from their environments and avoid installing or requiring this package. Employing package integrity verification and sourcing dependencies from trusted repositories is recommended. Monitor for any updates from the package publisher or security advisories for remediation guidance. Patch status is not yet confirmed — check the vendor advisory or trusted security sources for current remediation guidance.
Malicious code in bigops-operator-status (npm)
Description
The bigops-operator-status npm package version 35.4.5 contains malicious code that, upon being required, downloads and executes a platform-specific binary payload from obfuscated Cloudflare Workers hostnames or, if that fails, via a DNS-TXT covert channel. This payload is written to temporary directories, made executable, and run detached, enabling remote code execution. The payload sources are not controlled by the package publisher, and the binary content is opaque, indicating a fully functional remote code execution dropper triggered at module load.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The bigops-operator-status npm package version 35.4.5 includes malicious functionality in its _support.js module. When the package is loaded, it dynamically constructs obfuscated Cloudflare Workers hostnames to fetch a binary payload specific to the host platform (Linux, Darwin, Windows). This payload is saved to a disguised path in the system's temporary directory, permissions are set to executable, and it is executed detached from the main process. If the HTTPS fetch fails, the module falls back to retrieving the payload through a DNS-TXT record covert channel from multiple domains. The payload sources are external and not controlled by the package publisher, and the binary payload is opaque, making this a remote code execution dropper activated immediately upon module load.
Potential Impact
This malicious package enables remote code execution on any system that loads the affected version 35.4.5 of bigops-operator-status. The attacker can execute arbitrary binaries on the victim system with the privileges of the running process, potentially leading to full system compromise. The obfuscation and fallback mechanisms increase the difficulty of detection and mitigation.
Mitigation Recommendations
No official patch or remediation is currently documented for this malicious package version. Users should immediately remove version 35.4.5 of bigops-operator-status from their environments and avoid installing or requiring this package. Employing package integrity verification and sourcing dependencies from trusted repositories is recommended. Monitor for any updates from the package publisher or security advisories for remediation guidance. Patch status is not yet confirmed — check the vendor advisory or trusted security sources for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13230
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a738520bf8831d5394ef946
Added to database: 08/05/2026, 18:46:56 UTC
Last enriched: 08/05/2026, 22:46:03 UTC
Last updated: 08/05/2026, 22:46:03 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.