Malicious Code Vulnerability in @vampirchik147/libxmljs2 - Security Risk Identified
Summary
MAL-2026-1643: Malicious code in @vampirchik147/libxmljs2 (npm). Affects @vampirchik147/libxmljs2 versions 0.19.7. 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 package @vampirchik147/libxmljs2 is a JavaScript library that provides XML parsing capabilities for Node.js applications. It is designed to facilitate the manipulation and processing of XML data efficiently. However, this package has been flagged for containing malicious code, which poses a significant security risk to applications that depend on it.
Vulnerability Detail
The vulnerability stems from the inclusion of malicious code within the @vampirchik147/libxmljs2 package. This code can potentially compromise the security of applications using this library, leading to unauthorized access, data breaches, or other malicious activities. The specific version identified with this issue is 0.19.7, which has been linked to the malicious behavior. The origin of this vulnerability is attributed to the package being compromised, as noted by security researchers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @vampirchik147/libxmljs2If 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 avoid using the affected version of the package by uninstalling it with the following command:
npm uninstall @vampirchik147/libxmljs2
Then, you can explore alternative libraries for XML parsing that do not have known vulnerabilities.
Conclusion
The @vampirchik147/libxmljs2 package has been identified as containing malicious code, posing a serious security risk to applications that use it. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.
See every vulnerability recorded for @vampirchik147/libxmljs2 →
FAQ
The malicious code can lead to unauthorized access and potential data breaches in applications that utilize this library.
You can use Vulert, which monitors open-source vulnerabilities in real-time. Simply upload your package-lock.json file to check for any vulnerabilities.
Yes, you can temporarily uninstall the package and use alternative libraries for XML parsing until a secure version is available.
If you suspect that your application has been compromised, you should conduct a security audit, remove the malicious package, and review your application's security posture.
Detailed information can be found on the GitHub repository of the malicious package or through security advisories issued by organizations like ReversingLabs.
