Malicious Code Vulnerability in moudeva Package

moudeva Updated 23 Sep 2026

Summary

23/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16442: Malicious code in moudeva (npm). Affects moudeva versions 1.0.0. 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 moudeva package is an npm module designed for developers to facilitate various tasks within their applications. It is commonly used for its ease of integration and functionality. However, this package has been identified to contain malicious code that poses significant security risks, particularly through its use of child_process and hardcoded HTTP POST calls to a non-legitimate endpoint.

Vulnerability Detail

The vulnerability originates from the moudeva package's main.js file, which references the child_process module at multiple locations. It also makes HTTP POST calls to a hardcoded endpoint (ipc.shadxino.internal), which is not a publicly registrable domain. This indicates that the endpoint is likely controlled by an attacker, allowing for potential command execution and data exfiltration. The combination of these elements suggests that the package could be used to execute arbitrary commands and send sensitive data to an unauthorized location.

How To Fix

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

npm uninstall moudeva

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 moudeva package from your project until a secure version is released. You can do this by executing: npm uninstall moudeva. Additionally, consider using alternative packages that do not have known vulnerabilities.

Conclusion

The moudeva package has been identified to contain a serious vulnerability due to malicious code that can lead to command execution and data exfiltration. It is crucial for developers using this package to take immediate action by updating or removing it to safeguard their applications.

See every vulnerability recorded for moudeva →

Share this vulnerability

FAQ

The vulnerability involves malicious code that allows for command execution and data exfiltration through hardcoded HTTP POST requests.

You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

If an immediate update is not possible, consider removing the package from your project as a temporary measure.

While specific exploits have not been publicly disclosed, the nature of the vulnerability suggests that it could be exploited for unauthorized command execution.

Regularly check for updates to your packages and consider using tools like Vulert to receive real-time alerts about vulnerabilities.

How To Fix

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

npm uninstall moudeva

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