Which versions of ghazaly are malicious?

The following npm versions of ghazaly are flagged malicious: 99.9.0. Treat any of these as compromised.

How do I remediate ghazaly if I installed it?

Remove ghazaly from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed ghazaly — how do I know if it already compromised me?

If ghazaly was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is ghazaly part of a known attack campaign?

Yes — ghazaly is associated with the IN-MAL-2026-017387 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find ghazaly across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ghazaly (version 99.9.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ghazaly across your stack and pipelines.

Malicious package

ghazalynpm

ghazaly is a confirmed malicious npm package (MAL-2026-13755) that executes malicious code on install (malicious version 99.9.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ghazaly (npm)

MAL-2026-13755

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall ghazaly

What this malware does

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.

Malicious versions

1 flagged

99.9.0

Indicators of compromise (SHA-256)

d2054792481618ddf941c251fc0793ec8c1b85fe14107567b5c29cac9330d5be

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ghazaly (version 99.9.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ghazaly across your stack and pipelines.
If you installed it — respond
Remove ghazaly from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If ghazaly was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks ghazaly before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. ghazaly on npm has been identified as a malicious package (version 99.9.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017387

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ghazaly-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database