Malicious Package in nginxbeautifier
Summary
GHSA-28xx-8j99-m32j: Malicious Package in nginxbeautifier. Affects nginxbeautifier versions >= 1.0.14, < 1.0.15. Fixed in 1.0.15. 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
nginxbeautifier is an npm package that provides a tool for beautifying nginx configuration files. It is commonly used by developers and system administrators to improve the readability and organization of nginx configurations. However, version 1.0.14 of nginxbeautifier contained malicious code that posed a security risk to applications using this version.
Vulnerability Detail
The vulnerability in version 1.0.14 of nginxbeautifier allowed the execution of malicious code in the browser. When this code was triggered, it would search for password, cvc, and cardnumber fields in forms and extract their values. These extracted values were then sent to a remote server at https://js-metrics.com/minjs.php?pl=. This unauthorized data collection could potentially compromise sensitive user information, such as passwords and credit card details.
How To Fix
Minimum fixed version
1.0.15
This is the first release that contains the fix.
npm install nginxbeautifier@1.0.15Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Conclusion
Version 1.0.14 of nginxbeautifier contained a critical vulnerability that allowed the execution of malicious code in the browser. This code could extract sensitive user information and send it to a remote server. To mitigate this risk, it is crucial to replace version 1.0.14 with a safe version and evaluate the impact on user data. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for nginxbeautifier →
FAQ
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability. Vulert analyzes your package-lock.json file in real-time and alerts you about any open-source vulnerabilities, including this one.
The potential consequences of this vulnerability include unauthorized access to sensitive user information, such as passwords and credit card details. This can lead to identity theft, financial loss, and other security breaches.
No, only version 1.0.14 of nginxbeautifier is affected by this vulnerability. Versions before and after 1.0.14 are not compromised.
If your application is affected, you should immediately replace version 1.0.14 of nginxbeautifier with a safe version. Additionally, you should assess the potential impact on user data and take appropriate measures to secure and notify affected users.
No, there is no known workaround for this vulnerability. It is essential to update the package to a safe version as soon as possible.
