Malicious Code Detected in express-uatraits-mock Package

express-uatraits-mock Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20088: Malicious code in express-uatraits-mock (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The express-uatraits-mock package is a Node.js library designed for mocking traits in Express applications. It is commonly used by developers to facilitate testing and development by simulating various behaviors. However, this package has been identified 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 express-uatraits-mock 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. It is crucial for developers to be aware of this vulnerability to protect their applications from exploitation.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall express-uatraits-mock

If 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 express-uatraits-mock package in your application until a secure version is released. Consider using alternative mocking libraries that do not have known vulnerabilities.

Conclusion

The express-uatraits-mock package has been identified to contain malicious code, posing a significant risk to applications that utilize it. Developers are urged to remove the package and monitor for updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in your projects.

See every vulnerability recorded for express-uatraits-mock →

Share this vulnerability

FAQ

It is a Node.js library used for mocking traits in Express applications, aiding in testing and development.

The specific nature of the malicious code has not been disclosed, but it poses a risk of unauthorized access and data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Currently, there is no patched version available. It is advisable to remove the package until a secure version is released.

Remove the express-uatraits-mock package from your project and consider using alternative libraries for mocking.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall express-uatraits-mock

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback