Malicious Code Detected in wfui-test-e2e Package - Version 99.99.1

wfui-test-e2e Updated 02 Dec 2025

Summary

02/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191545: Malicious code in wfui-test-e2e (npm). Affects wfui-test-e2e versions 99.99.1. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The wfui-test-e2e package is an npm module designed for end-to-end testing in web applications. It provides tools and utilities to facilitate automated testing processes. However, version 99.99.1 of this package has been flagged for containing malicious code, which poses significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the wfui-test-e2e package arises from its communication with a domain linked to malicious activities and the execution of commands that are associated with harmful behavior. This can lead to unauthorized access, data breaches, and potential compromise of the systems using the package. The malicious nature of the package was identified by the OpenSSF Package Analysis project, which monitors and evaluates open-source packages for security threats.

How To Fix

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

npm uninstall wfui-test-e2e

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 remove the wfui-test-e2e package from your project until a secure version is released. You can do this by executing the command: npm uninstall wfui-test-e2e. Additionally, consider using alternative testing frameworks that do not have known vulnerabilities.

Conclusion

The wfui-test-e2e package version 99.99.1 has been identified as malicious, posing significant security risks to applications. It is crucial to update or remove this package to protect your systems from potential threats. Utilize tools like Vulert to monitor for vulnerabilities in your software.

See every vulnerability recorded for wfui-test-e2e →

Share this vulnerability

FAQ

wfui-test-e2e is an npm package used for end-to-end testing in web applications, providing tools for automated testing.

The malicious behavior was identified by the OpenSSF Package Analysis project, which monitors open-source packages for security threats.

Using the compromised version can lead to unauthorized access, data breaches, and potential system compromise.

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 removing the package temporarily and using alternative testing frameworks until a secure version is available.

How To Fix

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

npm uninstall wfui-test-e2e

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