Critical Malicious Code Vulnerability in grallama (npm)
Summary
MAL-2025-5780: Malicious code in grallama (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
Grallama is an npm package designed for various functionalities within JavaScript applications, often used for enhancing development workflows. However, it has been identified to contain embedded malicious code, making it a significant security risk. This vulnerability allows unauthorized access to systems where the package is installed, potentially compromising sensitive data and system integrity.
Vulnerability Detail
The vulnerability originates from the presence of embedded malicious code within the grallama package. This code can lead to full system compromise, allowing attackers to gain control over the affected systems. Users who have installed this package should consider their systems fully compromised, as the malicious code can exfiltrate sensitive information and manipulate system operations. The vulnerability is classified under CWE-506, indicating the presence of malicious code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall grallamaIf 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 measure, you can prevent the execution of the grallama package by removing it from your dependencies. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The discovery of malicious code in the grallama npm package poses a serious threat to users and their systems. Immediate action is required to mitigate risks, including uninstalling the package and monitoring for any signs of compromise. Utilizing tools like Vulert can aid in maintaining the security of your applications.
See every vulnerability recorded for grallama →
FAQ
Immediately uninstall the grallama package and rotate any secrets or keys stored on the affected system.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.
The risks include unauthorized access to your system, data exfiltration, and potential manipulation of system operations.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.
While many npm packages are safe, it is essential to vet packages before use and monitor for vulnerabilities regularly.
