Malicious Code Vulnerability in @gr-exports/body Package
Summary
MAL-2025-191561: Malicious code in @gr-exports/body (npm). Affects @gr-exports/body versions 1.0.0 – 99.0.0. 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 @gr-exports/body package is an npm library designed for managing and exporting body content in web applications. It is commonly used for its simplicity and efficiency in handling body data. However, this package has been identified as having a serious vulnerability that allows for the execution of malicious code, potentially compromising applications that rely on it.
Vulnerability Detail
The vulnerability stems from malicious code embedded within specific versions of the @gr-exports/body package. This code can execute unauthorized actions within the application, leading to data breaches, unauthorized access, and other security risks. The affected versions are 1.0.0 and 99.0.0, which were identified by security researchers from ReversingLabs. Users of these versions are at risk of exploitation, making it critical to address this issue promptly.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @gr-exports/bodyIf 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 remove the @gr-exports/body package from your project until a secure version is released. This can be done by running the following command: npm uninstall @gr-exports/body. Alternatively, consider using an alternative package that provides similar functionality without the associated risks.
Conclusion
The @gr-exports/body package has a significant vulnerability due to malicious code present in certain versions. It is crucial for developers using this package to update to a secure version or implement workarounds to mitigate risks. Regular monitoring of dependencies using tools like Vulert can help maintain application security.
See every vulnerability recorded for @gr-exports/body →
FAQ
The affected versions are 1.0.0 and 99.0.0.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.
If immediate updates are not possible, consider uninstalling the package or using an alternative until a secure version is available.
The vulnerability was discovered by security researchers at ReversingLabs.
The consequences can include unauthorized access to sensitive data, execution of malicious actions, and overall compromise of the application’s security.
