MalwarePublished 11 Aug 2026

ghazaly (npm) · Malicious Code

Affects ghazalySource GCVE Database

Malicious package : remove ghazaly and rotate any secrets on hosts that installed it.

Data as of 12 Aug 2026, 16:10 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-13755

What to do

Remove ghazaly from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmghazaly	Affected =99.9.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (d2054792481618ddf941c251fc0793ec8c1b85fe14107567b5c29cac9330d5be) package.json declares a postinstall hook that executes index.js on npm install. index.js requires os, https, and child_process, runs `whoami` via execSync, and reads os.hostname(), process.cwd(), and non-internal IPv4 addresses from os.networkInterfaces(). The collected host and identity data is sent as query-string parameters via https.get to a hardcoded Burp Collaborator subdomain (xghhv5sajm33m7krgi4n8my0mrsig84x.oastify.com). Package metadata is consistent with a dependency-confusion lure: version 99.9.0, empty author/description/keywords, and a nonsense dependency name `dependencyfsdsfdsfg` pinned to ^99.9.0. ## Source: ghsa-malware (30b6f1747cf452fcc6c383a05d4c901dd7da71fcae0757210cb361e408a73d6a) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

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.

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.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Aug 2026, 01:00 UTC

Technical details

References

Community reviews