Critical Malicious Code Vulnerability in selfsigned-certificate Package
Summary
MAL-2026-15623: Malicious code in selfsigned-certificate (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 selfsigned-certificate package is an npm module that allows users to generate self-signed SSL certificates for use in development and testing environments. It is commonly used in applications that require secure communications without the need for a certificate authority. However, this package has been compromised, leading to significant security risks for any system utilizing it.
Vulnerability Detail
The vulnerability stems from the presence of malicious code embedded within the selfsigned-certificate package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information, including secrets and keys. The origin of this issue is linked to a malicious actor who has manipulated the package, making it imperative for users to take immediate action to secure their systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall selfsigned-certificateIf 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, consider using alternative packages for generating self-signed certificates, such as 'pem' or 'node-forge', which do not have known vulnerabilities. You can install an alternative package using npm with the following command: npm install pem.
Conclusion
The selfsigned-certificate package has been compromised with malicious code, posing a significant risk to any system using it. Immediate removal of the package and rotation of sensitive information is essential. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.
See every vulnerability recorded for selfsigned-certificate →
FAQ
You should immediately remove the package and rotate any secrets or keys stored on your system.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest versions.
Failing to address this vulnerability can lead to unauthorized access to sensitive data and full control of your system by malicious actors.
Yes, but ensure you use a secure and trusted package that is not compromised. Consider alternatives to selfsigned-certificate.
