Malicious code in bigops-logs-player (npm)
The bigops-logs-player npm package version 35.2.8 contains malicious code that downloads and executes an OS-specific native binary from attacker-controlled infrastructure. It uses obfuscation techniques to hide Cloudflare Workers hostnames and employs a DNS-TXT covert channel as a fallback. The native binary is saved to temporary directories with disguised filenames and executed detached from the main process. This behavior is unrelated to the package's advertised logging functionality.
AI Analysis
Technical Summary
The bigops-logs-player package version 35.2.8 includes code in index.js that loads a polyfill script which reconstructs obfuscated Cloudflare Workers hostnames to evade static detection. It downloads a native binary specific to the operating system via HTTPS, writes it to a temporary directory under a disguised filename, sets executable permissions, and spawns it detached using system shells (/bin/sh or cmd.exe). If the primary hosts are unreachable, it uses a DNS-TXT covert channel to resolve alternate hosts under *.dl.wel1.ru, also obfuscated. Execution is gated by freshness markers and environment opt-outs to reduce detection noise. This malicious behavior is unrelated to the package's stated purpose as a log transport library.
Potential Impact
The malicious code enables remote code execution by downloading and running attacker-controlled native binaries on the host system. This can lead to full system compromise, data theft, or further malware deployment. The obfuscation and covert channel techniques complicate detection and analysis. Since the package masquerades as a legitimate logging library, users may inadvertently install and execute this malware.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should immediately stop using bigops-logs-player version 35.2.8 and remove it from their environments. Avoid installing or running this package from untrusted sources. Monitor for any processes spawned from temporary directories with suspicious names. Consider using trusted package registries and scanning tools to detect malicious packages. Patch status is not yet confirmed — check the vendor advisory or trusted security sources for updates.
Malicious code in bigops-logs-player (npm)
Description
The bigops-logs-player npm package version 35.2.8 contains malicious code that downloads and executes an OS-specific native binary from attacker-controlled infrastructure. It uses obfuscation techniques to hide Cloudflare Workers hostnames and employs a DNS-TXT covert channel as a fallback. The native binary is saved to temporary directories with disguised filenames and executed detached from the main process. This behavior is unrelated to the package's advertised logging functionality.
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-logs-player package version 35.2.8 includes code in index.js that loads a polyfill script which reconstructs obfuscated Cloudflare Workers hostnames to evade static detection. It downloads a native binary specific to the operating system via HTTPS, writes it to a temporary directory under a disguised filename, sets executable permissions, and spawns it detached using system shells (/bin/sh or cmd.exe). If the primary hosts are unreachable, it uses a DNS-TXT covert channel to resolve alternate hosts under *.dl.wel1.ru, also obfuscated. Execution is gated by freshness markers and environment opt-outs to reduce detection noise. This malicious behavior is unrelated to the package's stated purpose as a log transport library.
Potential Impact
The malicious code enables remote code execution by downloading and running attacker-controlled native binaries on the host system. This can lead to full system compromise, data theft, or further malware deployment. The obfuscation and covert channel techniques complicate detection and analysis. Since the package masquerades as a legitimate logging library, users may inadvertently install and execute this malware.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should immediately stop using bigops-logs-player version 35.2.8 and remove it from their environments. Avoid installing or running this package from untrusted sources. Monitor for any processes spawned from temporary directories with suspicious names. Consider using trusted package registries and scanning tools to detect malicious packages. Patch status is not yet confirmed — check the vendor advisory or trusted security sources for updates.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13223
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a738520bf8831d5394ef917
Added to database: 08/05/2026, 18:46:56 UTC
Last enriched: 08/05/2026, 22:47:01 UTC
Last updated: 08/05/2026, 22:47:01 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.