Critical Malicious Code Vulnerability in awsm-acslibs Package
Summary
MAL-2026-130: Malicious code in awsm-acslibs (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 awsm-acslibs package is a library used in Node.js applications to facilitate various functionalities related to AWS services. It is designed to streamline the integration of AWS features into applications, providing developers with a set of tools to enhance their software. However, this package has been identified as containing malicious code, posing significant security risks to any system utilizing it.
Vulnerability Detail
The vulnerability stems from the presence of embedded malicious code within the awsm-acslibs package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to a malicious actor who has manipulated the package, leading to potential full control of the affected systems. Users are advised to treat any system running this package as fully compromised.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall awsm-acslibsIf 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 the system. Users should ensure that all sensitive data is rotated and that the system is monitored for any signs of compromise.
Conclusion
The awsm-acslibs package has been identified as containing malicious code that poses significant risks to any system using it. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert to monitor for vulnerabilities in their applications.
See every vulnerability recorded for awsm-acslibs →
FAQ
Immediately remove the awsm-acslibs package and rotate any secrets or keys stored on the affected system.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Failing to address this vulnerability can lead to unauthorized access to sensitive information and potential full control of your system by malicious actors.
Yes, Vulert provides a service that monitors your package-lock.json file for open-source vulnerabilities in real-time.
It is advisable to avoid using the awsm-acslibs package until it has been verified as safe and free from malicious code.
