Critical Malicious Code Vulnerability in typed-document-node Package
Summary
MAL-2026-667: Malicious code in typed-document-node (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 typed-document-node package is a widely used library in the npm ecosystem that facilitates the creation and manipulation of typed document nodes in JavaScript applications. It is designed to enhance type safety and improve developer experience by providing a structured way to work with GraphQL documents. However, this package has been found to contain malicious code, posing significant security risks to applications that utilize it.
Vulnerability Detail
The vulnerability in the typed-document-node package stems from the presence of embedded malicious code. 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 code was identified through sources like Amazon Inspector and GHSA malware reports, indicating that systems running this package should be considered fully compromised. The implications of this vulnerability are severe, as it may lead to data breaches and unauthorized control over affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall typed-document-nodeIf 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 temporary workaround, you can isolate the affected application from the network and refrain from using any sensitive data until the package is removed and the system is secured. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The discovery of malicious code within the typed-document-node package poses a significant threat to applications using it. Immediate action is required to remove the package and secure any potentially compromised information. Utilizing tools like Vulert can help monitor and manage vulnerabilities in your software effectively.
See every vulnerability recorded for typed-document-node →
FAQ
You should remove the typed-document-node package from your project immediately and rotate any sensitive information that may have been compromised.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By utilizing the Vulert playground, you can check if your application is affected without any signup.
Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential control by malicious entities over your application.
As of now, there is no specific patch version available. The recommended action is to remove the package entirely.
It is highly discouraged to use typed-document-node due to the identified malicious code. Consider looking for alternative packages that provide similar functionality.
