Malicious code in @omniwatch-wick/cli (npm)
The npm package @omniwatch-wick/cli version 0.1.2 contains malicious code that collects host system identifiers and user information, then exfiltrates this data to attacker-controlled endpoints. This behavior is not part of any documented CLI functionality and represents an installer-side reconnaissance and data exfiltration beacon. Installation of this package can lead to full system compromise, requiring immediate secret and key rotation from a different machine. Removal of the package alone may not eliminate all malicious software introduced.
AI Analysis
Technical Summary
The @omniwatch-wick/cli npm package version 0.1.2 includes code that requires modules such as child_process, os, http, and https to gather host identifiers including user info, hostname, and platform. It sends this information via POST requests to hardcoded, non-first-party Cloudflare Workers endpoints controlled by the package publisher. This exfiltration behavior indicates malicious intent, functioning as a reconnaissance and data collection beacon during installation. According to the ghsa-malware source, any system with this package installed should be considered fully compromised, with secrets and keys rotated immediately. The package removal does not guarantee full remediation due to potential additional malware.
Potential Impact
Systems with @omniwatch-wick/cli version 0.1.2 installed are at high risk of full compromise. Sensitive host and user identity data is exfiltrated to attacker-controlled servers. Attackers may have gained persistent access, and all secrets and keys stored on the compromised system should be considered exposed and rotated. The presence of this package indicates a severe security breach with potential for further undetected malicious activity.
Mitigation Recommendations
Immediate removal of the @omniwatch-wick/cli package version 0.1.2 is required. However, removal alone is insufficient due to the likelihood of additional malware. All secrets and keys stored on the compromised system must be rotated from a separate, trusted machine. Conduct a thorough investigation and system remediation to identify and eliminate any residual malicious software. Monitor for any unusual activity and consider rebuilding the affected system if full remediation cannot be assured.
Malicious code in @omniwatch-wick/cli (npm)
Description
The npm package @omniwatch-wick/cli version 0.1.2 contains malicious code that collects host system identifiers and user information, then exfiltrates this data to attacker-controlled endpoints. This behavior is not part of any documented CLI functionality and represents an installer-side reconnaissance and data exfiltration beacon. Installation of this package can lead to full system compromise, requiring immediate secret and key rotation from a different machine. Removal of the package alone may not eliminate all malicious software introduced.
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 @omniwatch-wick/cli npm package version 0.1.2 includes code that requires modules such as child_process, os, http, and https to gather host identifiers including user info, hostname, and platform. It sends this information via POST requests to hardcoded, non-first-party Cloudflare Workers endpoints controlled by the package publisher. This exfiltration behavior indicates malicious intent, functioning as a reconnaissance and data collection beacon during installation. According to the ghsa-malware source, any system with this package installed should be considered fully compromised, with secrets and keys rotated immediately. The package removal does not guarantee full remediation due to potential additional malware.
Potential Impact
Systems with @omniwatch-wick/cli version 0.1.2 installed are at high risk of full compromise. Sensitive host and user identity data is exfiltrated to attacker-controlled servers. Attackers may have gained persistent access, and all secrets and keys stored on the compromised system should be considered exposed and rotated. The presence of this package indicates a severe security breach with potential for further undetected malicious activity.
Mitigation Recommendations
Immediate removal of the @omniwatch-wick/cli package version 0.1.2 is required. However, removal alone is insufficient due to the likelihood of additional malware. All secrets and keys stored on the compromised system must be rotated from a separate, trusted machine. Conduct a thorough investigation and system remediation to identify and eliminate any residual malicious software. Monitor for any unusual activity and consider rebuilding the affected system if full remediation cannot be assured.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10486
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a55ff9e68715ace432f6be5
Added to database: 07/14/2026, 09:21:34 UTC
Last enriched: 07/30/2026, 09:21:37 UTC
Last updated: 07/30/2026, 09:21:37 UTC
Views: 8
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.