Malicious code in ubermenu (npm)

ubermenu Updated 02 Oct 2025

Summary

29/09/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8261: Malicious code in ubermenu (npm). Affects ubermenu versions 3.3.3. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The ubermenu package is an npm package that provides a menu plugin for websites. It allows developers to create highly customizable menus with various features and styles. The package is widely used in web development projects to enhance the navigation experience for users. However, a specific version of ubermenu (3.3.3) has been identified as malicious by the OpenSSF Package Analysis project.

Vulnerability Detail

The identified version of ubermenu (3.3.3) is considered malicious due to its communication with a domain associated with malicious activity and its execution of commands associated with malicious behavior. This poses a significant security risk to websites and applications that utilize this version of ubermenu. The malicious code could potentially compromise user data, introduce vulnerabilities for further exploitation, or perform unauthorized actions on the affected system.

How To Fix

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

npm uninstall ubermenu

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 is no specific workaround provided for this vulnerability. The best course of action is to follow the steps mentioned in the 'how_to_fix' section and remove the affected version of ubermenu from your project.

Conclusion

The identified version of ubermenu (3.3.3) has been flagged as malicious due to its association with a domain involved in malicious activity and its execution of commands associated with malicious behavior. It is crucial for developers using ubermenu to remove this specific version from their projects and update to a non-malicious version or consider alternative menu plugins. Prompt action is necessary to protect user data and prevent potential security breaches. For further assistance and guidance, please contact DevNack.com.

See every vulnerability recorded for ubermenu →

Share this vulnerability

FAQ

You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this specific vulnerability. Simply upload your package-lock.json file to the playground, and it will provide you with real-time alerts and information about any open-source vulnerabilities, including this one.

No, only version 3.3.3 of ubermenu has been identified as malicious. It is crucial to check the version of ubermenu used in your project and ensure that it is not the affected version.

The malicious code in ubermenu can lead to various consequences, including data breaches, unauthorized access to sensitive information, and potential compromise of the affected system. It is essential to address this vulnerability promptly to mitigate these risks.

Yes, there are several alternative menu plugins available in the npm ecosystem. Some popular options include 'react-burger-menu', 'react-responsive-menu', and 'react-contextmenu'. It is recommended to evaluate these alternatives and choose one that meets your project's requirements while ensuring it is free from any known vulnerabilities.

If you have any further questions or need assistance with vulnerability remediation, you can reach out to info@devnack.com. They can provide you with expert guidance and support in addressing this vulnerability.

How To Fix

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

npm uninstall ubermenu

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