Critical Malicious Code Vulnerability in aurora-scribe Package
Summary
MAL-2025-15061: Malicious code in aurora-scribe (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 aurora-scribe package is an npm library designed for logging and managing data streams in Node.js applications. It offers features such as customizable logging levels and integration with various data sources. However, it has been identified to contain malicious code, posing significant risks to applications that utilize it.
Vulnerability Detail
The vulnerability in the aurora-scribe package originates from the inclusion of malicious code that can compromise the security of applications using this library. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The issue affects all versions starting from 0, making it critical for users to take immediate action.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall aurora-scribeIf 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 workaround, you can avoid using the aurora-scribe package altogether and implement alternative logging solutions that do not pose security risks. Consider using well-established libraries such as Winston or Bunyan for logging purposes.
Conclusion
The discovery of malicious code within the aurora-scribe package poses a significant threat to applications utilizing this library. Immediate action is required to remove the package and replace it with a secure alternative to safeguard your applications from potential exploits.
See every vulnerability recorded for aurora-scribe →
FAQ
The malicious code is designed to exploit vulnerabilities in applications, potentially leading to unauthorized access and data breaches.
You can use tools like Vulert to monitor and alert for open-source vulnerabilities. Check your package-lock.json file for any affected packages.
Currently, the best mitigation strategy is to remove the aurora-scribe package and replace it with a secure alternative.
Immediately assess your applications for any signs of compromise and remove the aurora-scribe package. Consider conducting a security audit.
You can use the Vulert playground to check if your application is affected by this vulnerability without requiring any signup.
