Critical Malicious Code Vulnerability in nad-home Package

nad-home Updated 16 Dec 2025

Summary

16/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192592: Malicious code in nad-home (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The nad-home package is an npm module designed for home automation and control. It allows users to integrate various smart home devices and manage them through a unified interface. However, this package has been found to contain malicious code that compromises the security of any system it is installed on, making it a significant risk for users and developers alike.

Vulnerability Detail

The nad-home package has been identified as containing embedded malicious code, which poses a severe threat to any computer that has this package installed. The origin of this vulnerability is linked to the package's malicious intent, which can lead to full system compromise. Users should be aware that all secrets and keys stored on the affected computer should be rotated immediately from a secure device, as the malicious code may allow external entities to gain control over the system.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall nad-home

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

Currently, there are no effective workarounds to mitigate the risks posed by the nad-home package. The only recommended action is to uninstall the package and rotate all sensitive credentials.

Conclusion

The nad-home package has been identified as containing malicious code that poses a significant risk to users. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to monitor their systems and utilize tools like Vulert for ongoing vulnerability management.

See every vulnerability recorded for nad-home →

Share this vulnerability

FAQ

You should immediately uninstall the nad-home package and rotate all sensitive credentials stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Keeping the nad-home package installed can lead to full system compromise, allowing malicious actors to access sensitive information and control your system.

While removing the package is essential, there is no guarantee that all malicious software will be eliminated. It is advisable to perform a complete system audit and consider restoring from a backup.

If a patched version is released, updating to that version may resolve the vulnerability. However, it is crucial to first remove the compromised package.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall nad-home

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback