Critical Malicious Code Vulnerability in @fxinternal/netdiagnostics Package
Summary
MAL-2026-718: Malicious code in @fxinternal/netdiagnostics (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The @fxinternal/netdiagnostics package is a Node.js library designed for network diagnostics and monitoring. It is commonly used in applications that require network performance analysis and troubleshooting. However, this package has been identified to contain malicious code, posing significant risks to systems that utilize it.
Vulnerability Detail
The vulnerability originates from the presence of embedded malicious code within the @fxinternal/netdiagnostics package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code means that simply removing the package may not eliminate all threats, as full control of the affected system may have been granted to an external entity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @fxinternal/netdiagnosticsIf 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
As a workaround, it is recommended to immediately cease the use of any applications relying on the @fxinternal/netdiagnostics package and to monitor your systems for any suspicious activity. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The @fxinternal/netdiagnostics package has been identified as containing malicious code, posing significant risks to systems using it. Immediate action is required to uninstall the package and secure any potentially compromised information. Monitoring tools like Vulert can assist in identifying vulnerabilities in your applications.
See every vulnerability recorded for @fxinternal/netdiagnostics →
FAQ
You should uninstall the package immediately and rotate any sensitive information that may have been exposed.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
While removing the package is necessary, there is no guarantee that all malicious software will be eliminated. It is advisable to perform a thorough security audit of your system.
The consequences include unauthorized access to sensitive data, potential system compromise, and the risk of further malicious activities on the affected system.
If a patched version is released, updating the package will help mitigate the vulnerability. However, it is essential to first remove the compromised version.
