Critical Malicious Code Vulnerability in okta-loginpage-render Package
Summary
MAL-2026-92: Malicious code in okta-loginpage-render (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 okta-loginpage-render package is an npm library designed for rendering login pages for Okta authentication. It is widely used in web applications to facilitate secure user authentication. However, this package has been compromised, embedding malicious code that poses significant security risks to any system that installs it.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the okta-loginpage-render 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 malicious nature of this code is classified under CWE-506, indicating that the product contains code that appears to be malicious. Users are advised to treat any system with this package as compromised and take immediate action.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall okta-loginpage-renderIf 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
There are no effective workarounds for this vulnerability other than removing the package. It is crucial to ensure that no remnants of the malicious code remain on the system after uninstallation.
Conclusion
The okta-loginpage-render package has been identified as containing malicious code that poses serious security threats. Immediate removal of the package is necessary to protect your system. Regular monitoring and using tools like Vulert can help prevent similar vulnerabilities in the future.
See every vulnerability recorded for okta-loginpage-render →
FAQ
You should immediately uninstall the package using 'npm uninstall okta-loginpage-render' and rotate any secrets or keys stored on the affected system.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
Failing to remove the package can lead to unauthorized access to sensitive information, potentially compromising your entire system and exposing it to further attacks.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to minimize the risk of vulnerabilities.
Yes, you can use other official Okta libraries or implement your own authentication mechanism without relying on the compromised package.
