Which versions of hl-naduccio are malicious?

The following npm versions of hl-naduccio are flagged malicious: 1.0.7. Treat any of these as compromised.

How do I remediate hl-naduccio if I installed it?

Remove hl-naduccio 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 hl-naduccio — how do I know if it already compromised me?

If hl-naduccio 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 hl-naduccio part of a known attack campaign?

Yes — hl-naduccio is associated with the GHSA-2rqw-9jfq-33mm 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 hl-naduccio 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 hl-naduccio (version 1.0.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hl-naduccio across your stack and pipelines.

Malicious package

hl-naduccionpm

Malicious code in hl-naduccio (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191538

Immediate action

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

npm uninstall hl-naduccio

What this malware does

The package hl-naduccio was found to contain malicious code.

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.

The OpenSSF Package Analysis project identified 'hl-naduccio' @ 1.0.7 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

1.0.7

Indicators of compromise (SHA-256)

0b241e02035aedcc9558ceaca424595a56ae6ec57ab533d7e525f99320d8883d

f7193ea32e3d2686d1c8a3d6a7f78a78a41f3d8cf1441595f7a323029b4b9ac7

cbf2d782795965491bb5f2dbaa4d5cf378b7ccfd4b370b90cb7059b01b2685ab

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 hl-naduccio (version 1.0.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hl-naduccio across your stack and pipelines.
If you installed it — respond
Remove hl-naduccio 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 hl-naduccio 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 hl-naduccio 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. hl-naduccio on npm has been identified as a malicious package (version 1.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-2rqw-9jfq-33mm

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks hl-naduccio-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