Which versions of nad-home are malicious?

The following npm versions of nad-home are flagged malicious: 999.0.103, 999.0.104. Treat any of these as compromised.

How do I remediate nad-home if I installed it?

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

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

Yes — nad-home is associated with the GHSA-3j59-8fh5-f32x, RLMA-2026-01440 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 nad-home 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 nad-home (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nad-home across your stack and pipelines.

Malicious package

nad-homenpm

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

MAL-2025-192592

Immediate action

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

npm uninstall nad-home

What this malware does

The package nad-home 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.

Malicious versions

2 flagged

999.0.103999.0.104

Indicators of compromise (SHA-256)

5d84934ad23672579c5ab6e2f431b6f1b99a7a8f0e872a628503037c6298f8d4

34249dc2bb9d97e2f560efbcef33d2f0f0de8cb15f9c66a984697700d6b92d43

354e509fcdc07a810a2ff0ad48510fcd0183e353eca019d977bd73362a7383be

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

Campaign

GHSA-3j59-8fh5-f32xRLMA-2026-01440

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks nad-home-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