Critical Malicious Code Vulnerability in @osmanekrem/bmad Package
Summary
MAL-2025-191046: Malicious code in @osmanekrem/bmad (npm). Affects @osmanekrem/bmad versions 1.0.6. 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 @osmanekrem/bmad package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for its features, but it has been identified as containing malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk to users and their data.
Vulnerability Detail
The vulnerability originates from the presence of embedded malicious code within the @osmanekrem/bmad package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications include potential data breaches and loss of control over the affected systems. Users are advised to treat any system running this package as compromised.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @osmanekrem/bmadIf 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, users should uninstall the package using the command: npm uninstall @osmanekrem/bmad. Additionally, ensure that all sensitive information is rotated and monitored for any unauthorized access.
Conclusion
The @osmanekrem/bmad package has been identified as containing malicious code that poses a serious security risk. Users must take immediate action to remove the package and secure their systems. Continuous monitoring and verification of dependencies are crucial to maintaining software security.
See every vulnerability recorded for @osmanekrem/bmad →
FAQ
Immediately uninstall the package and rotate all sensitive information stored on the affected system.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without requiring any signup.
Currently, there is no patched version available. Users should focus on uninstalling the package and securing their systems.
Failing to address this vulnerability can lead to unauthorized access to sensitive data and complete control of your system by malicious actors.
While many npm packages are safe, it is essential to monitor and verify the packages you use. Tools like Vulert can help you stay informed about vulnerabilities.
