Malicious Code Detected in usaa-authentication-mocks Package
Summary
MAL-2026-25: Malicious code in usaa-authentication-mocks (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 usaa-authentication-mocks package is an npm library designed to simulate authentication processes for applications that require user login functionalities. It is commonly used in testing environments to create mock responses for user authentication without needing to connect to a real authentication service. However, this package has been found to contain malicious code, posing a significant risk to applications that utilize it.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the usaa-authentication-mocks package. This code can potentially compromise the security of applications that depend on this package, leading to unauthorized access, data breaches, or other malicious activities. The specific technical details of the malicious code have not been disclosed, but its presence indicates a severe risk to any software utilizing this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall usaa-authentication-mocksIf 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 replace the usaa-authentication-mocks package with an alternative mocking library that does not have known vulnerabilities. Consider using libraries such as 'auth0-js' or 'passport' for authentication mocking in your tests.
Conclusion
The discovery of malicious code in the usaa-authentication-mocks package poses a serious threat to applications that utilize it. It is crucial for developers to take immediate action by removing the package and considering alternative solutions to ensure the security of their applications.
See every vulnerability recorded for usaa-authentication-mocks →
FAQ
It is an npm library used to simulate authentication processes for testing applications.
The malicious code can lead to unauthorized access and potential data breaches in applications that use the package.
You should remove the package immediately and replace it with a secure alternative.
Yes, you can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
