Critical Malicious Code Vulnerability in @asyncapi/java-spring-template Package
Summary
MAL-2025-190716: Malicious code in @asyncapi/java-spring-template (npm). Affects @asyncapi/java-spring-template versions 1.6.1 – 1.6.2. 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 @asyncapi/java-spring-template package is a Java Spring template designed for building applications that utilize the AsyncAPI specification. It provides developers with tools and templates to streamline the development process. However, this package has been found to contain malicious code, posing significant security risks to any system that has it installed.
Vulnerability Detail
The vulnerability stems from the presence of embedded malicious code within the @asyncapi/java-spring-template package. This code can compromise any computer running the package, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code means that even after removal of the package, there is no guarantee that all traces of the malicious software will be eliminated, potentially leaving the system vulnerable to further attacks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @asyncapi/java-spring-templateIf 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 avoid using the @asyncapi/java-spring-template package until a verified safe version is released. Monitor your application for any signs of compromise and consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The discovery of malicious code within the @asyncapi/java-spring-template package poses a serious threat to users. Immediate action is required to mitigate risks, including the removal of the package and rotation of sensitive information. Users are encouraged to monitor their systems and consider alternative solutions until a safe version is available.
See every vulnerability recorded for @asyncapi/java-spring-template →
FAQ
Immediately remove the package and rotate all secrets and keys stored on the affected machine.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without any signup.
Currently, there is no specific patch available, but it is advised to update to the latest version of the package if released.
Failure to address this vulnerability can lead to unauthorized access to sensitive data and potential control over your system by malicious actors.
No, removing the package does not guarantee that all malicious software has been eliminated. A thorough security audit is recommended.
References
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.