Critical Malicious Code Vulnerability in mayhem-wma Package

mayhem-wma Updated 25 Nov 2025

Summary

25/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191464: Malicious code in mayhem-wma (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 mayhem-wma package is an npm library designed for specific functionalities related to media processing. However, it has been identified as containing malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk to users, as it can lead to unauthorized access and data breaches.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the mayhem-wma package. This code can fully compromise any computer that has the package installed, allowing external entities to gain control over the system. The ramifications include potential data theft, unauthorized access to sensitive information, and the possibility of further malware installation. The vulnerability is classified under CWE-506, which indicates that the product contains embedded malicious code.

How To Fix

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

npm uninstall mayhem-wma

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

There are no effective workarounds for this vulnerability. The best course of action is to remove the package entirely and ensure that your system is secure.

Conclusion

The mayhem-wma package has been identified as containing malicious code that poses a serious security risk. Immediate action is required to uninstall the package and secure your system. Regular monitoring for vulnerabilities using tools like Vulert can help prevent such issues in the future.

See every vulnerability recorded for mayhem-wma →

Share this vulnerability

FAQ

You should uninstall the mayhem-wma package immediately and rotate any sensitive information stored on your system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

Keeping mayhem-wma installed can lead to unauthorized access to your system, data breaches, and further malware infections.

After removing the package, you should rotate all secrets and keys and perform a thorough security audit of your system.

Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software, providing an easy way to stay informed.

How To Fix

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

npm uninstall mayhem-wma

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