Critical Malicious Code Vulnerability in template-micro-service Package
Summary
MAL-2025-191022: Malicious code in template-micro-service (npm). Affects template-micro-service versions 1.0.2 – 1.0.3. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The template-micro-service package is an npm library designed to facilitate the development of microservices. It provides essential functionalities for building and deploying microservices efficiently. However, recent findings have revealed that this package contains malicious code, posing significant security risks to systems utilizing it.
Vulnerability Detail
The vulnerability stems from the presence of embedded malicious code within the template-micro-service package. This code can compromise any system where the package is installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code has been confirmed by both Amazon Inspector and GHSA, indicating that systems running this package should be considered fully compromised.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall template-micro-serviceIf 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
There are no effective workarounds for this vulnerability other than removing the package and securing your system. It is essential to monitor your environment for any signs of compromise.
Conclusion
The discovery of malicious code in the template-micro-service package highlights the importance of vigilance in managing open-source dependencies. Immediate action is required to mitigate risks associated with this vulnerability, including uninstalling the affected package and securing any compromised secrets.
See every vulnerability recorded for template-micro-service →
FAQ
You should immediately uninstall the package and rotate any secrets or keys that may have been compromised.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
Versions 1.0.2 and 1.0.3 of the template-micro-service package are confirmed to contain malicious code.
While removing the package is a critical step, you should also ensure that your system is secure and monitor for any signs of compromise.
While many npm packages are safe, it is essential to regularly audit and monitor your dependencies for vulnerabilities.
References
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
