Critical Malicious Code Vulnerability in ash-history Package
Summary
MAL-2025-14899: Malicious code in ash-history (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 ash-history package is a JavaScript library used in web applications for managing browser history. It provides developers with tools to manipulate the history stack, enabling features like navigation and state management. However, this package has been found to contain malicious code, posing significant risks to applications that depend on it.
Vulnerability Detail
The vulnerability in the ash-history package stems from the inclusion of malicious code that can compromise the security of applications using it. This code can lead to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for developers to address this vulnerability promptly.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ash-historyIf 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
If immediate updating is not feasible, consider removing the ash-history package from your project until a secure version is available. You can do this by executing: npm uninstall ash-history.
Conclusion
The ash-history package has a critical vulnerability due to the presence of malicious code. Developers are urged to update to a patched version or remove the package entirely to protect their applications. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.
See every vulnerability recorded for ash-history →
FAQ
The ash-history package is used for managing browser history in web applications, allowing developers to control navigation and state.
The malicious code can lead to unauthorized access and potential data breaches, affecting the security of applications that utilize the package.
You can use Vulert, which monitors open-source vulnerabilities in real-time. By analyzing your package-lock.json file, Vulert can alert you to any vulnerabilities, including those in ash-history.
Yes, you can temporarily remove the ash-history package from your project until a secure version is released.
Detailed information about the vulnerability can be found on the GitHub repository of the malicious packages project.
