Malicious code in ghazaly (npm)
The npm package 'ghazaly' version 99.9.0 contains malicious code that executes during installation. It collects host identity information and sends it to an attacker-controlled server. This package is considered fully compromising any system where it is installed, requiring immediate secret and key rotation. Removal of the package does not guarantee full remediation due to potential persistent control by the attacker.
AI Analysis
Technical Summary
The 'ghazaly' npm package version 99.9.0 includes a postinstall script that runs index.js, which executes system commands and gathers host information such as the current user, hostname, working directory, and network interfaces. This data is exfiltrated via HTTPS GET requests to a hardcoded Burp Collaborator subdomain, indicating malicious intent. The package metadata suggests it is a dependency confusion lure with suspicious versioning and dependency naming. The presence of this package on a system implies a full compromise, with potential persistent malicious control beyond just the package itself.
Potential Impact
Any system with 'ghazaly' version 99.9.0 installed is considered fully compromised. The attacker gains access to sensitive host information and potentially full control over the system. All secrets and keys stored on the compromised system should be considered exposed and must be rotated immediately from a secure environment. Simply removing the package does not guarantee removal of all malicious components or backdoors.
Mitigation Recommendations
Remove the 'ghazaly' package version 99.9.0 immediately from affected systems. Rotate all secrets, keys, and credentials that were stored or used on the compromised system from a different, secure computer. Conduct a thorough investigation for any persistent malicious activity or backdoors, as removal of the package alone may not fully remediate the compromise. Monitor for any unusual activity and consider rebuilding the system if full trust cannot be restored.
Malicious code in ghazaly (npm)
Description
The npm package 'ghazaly' version 99.9.0 contains malicious code that executes during installation. It collects host identity information and sends it to an attacker-controlled server. This package is considered fully compromising any system where it is installed, requiring immediate secret and key rotation. Removal of the package does not guarantee full remediation due to potential persistent control by the attacker.
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 'ghazaly' npm package version 99.9.0 includes a postinstall script that runs index.js, which executes system commands and gathers host information such as the current user, hostname, working directory, and network interfaces. This data is exfiltrated via HTTPS GET requests to a hardcoded Burp Collaborator subdomain, indicating malicious intent. The package metadata suggests it is a dependency confusion lure with suspicious versioning and dependency naming. The presence of this package on a system implies a full compromise, with potential persistent malicious control beyond just the package itself.
Potential Impact
Any system with 'ghazaly' version 99.9.0 installed is considered fully compromised. The attacker gains access to sensitive host information and potentially full control over the system. All secrets and keys stored on the compromised system should be considered exposed and must be rotated immediately from a secure environment. Simply removing the package does not guarantee removal of all malicious components or backdoors.
Defensive Guidance
Remove the 'ghazaly' package version 99.9.0 immediately from affected systems. Rotate all secrets, keys, and credentials that were stored or used on the compromised system from a different, secure computer. Conduct a thorough investigation for any persistent malicious activity or backdoors, as removal of the package alone may not fully remediate the compromise. Monitor for any unusual activity and consider rebuilding the system if full trust cannot be restored.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13755
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-g62q-mq3x-765x"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a7bc14ebf8831d539b1562d
Added to database: 08/12/2026, 00:41:50 UTC
Last enriched: 08/12/2026, 01:00:11 UTC
Last updated: 08/12/2026, 01:49:26 UTC
Views: 4
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.