Malicious Code Detected in Midway-Dataproxy Package - MAL-2025-26310

midway-dataproxy Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-26310: Malicious code in midway-dataproxy (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The 'midway-dataproxy' package is a Node.js library designed to facilitate data proxying in applications built with the Midway framework. It provides developers with tools to manage data flow efficiently between different services. However, this package has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the 'midway-dataproxy' package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code could potentially allow unauthorized access to sensitive data, lead to data manipulation, or even facilitate further attacks on the application or its users. The issue was introduced in version 0 and affects all subsequent versions.

How To Fix

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

npm uninstall midway-dataproxy

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 measure, you can avoid using the 'midway-dataproxy' package until a secure version is released. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The 'midway-dataproxy' package has been identified to contain malicious code, posing serious security risks to applications. It is crucial for developers to remove this package and seek alternatives until a secure version is available. Utilizing tools like Vulert can help in monitoring for such vulnerabilities effectively.

See every vulnerability recorded for midway-dataproxy →

Share this vulnerability

FAQ

It is a Node.js library used for data proxying in applications built with the Midway framework.

The malicious code can compromise application security, potentially allowing unauthorized access and data manipulation.

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.

Remove the package from your project and consider using a secure alternative until a patched version is released.

As of now, no patched version has been released. Monitor the package repository for updates.

Related vulnerabilities

Recent vulnerabilities recorded for midway-dataproxy.

How To Fix

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

npm uninstall midway-dataproxy

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