Malicious Code Detected in mpesa-ui-components: A Critical Security Concern

mpesa-ui-components Updated 02 Oct 2025

Summary

30/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6736: Malicious code in mpesa-ui-components (npm). Affects mpesa-ui-components versions >= 1.5.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 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 mpesa-ui-components package is a JavaScript library designed for integrating M-Pesa payment solutions into web applications. It provides developers with tools to facilitate transactions and manage payment workflows seamlessly. However, this package has been identified as having a vulnerability that allows it to communicate with a domain associated with malicious activities, posing a significant risk to users and their data.

Vulnerability Detail

The vulnerability in the mpesa-ui-components package originates from version 1.5.0, where the package is found to communicate with a domain linked to malicious activities. This communication can potentially lead to data breaches, unauthorized access, and exploitation of sensitive user information. The presence of such malicious code undermines the integrity of applications using this package, making it imperative for developers to address this issue promptly.

How To Fix

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

npm uninstall mpesa-ui-components

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 may consider removing the mpesa-ui-components package from your project until a secure version is released. This can be done by executing the following command: npm uninstall mpesa-ui-components. Additionally, review your application for any dependencies that may rely on this package and assess their security.

Conclusion

The mpesa-ui-components package has been identified with a serious vulnerability that allows it to communicate with a malicious domain. Developers using this package should take immediate action to update or remove it to protect their applications and users. Utilizing tools like Vulert can help in monitoring and managing such vulnerabilities effectively.

See every vulnerability recorded for mpesa-ui-components →

Share this vulnerability

FAQ

The vulnerability involves the package communicating with a domain associated with malicious activities, which can compromise user data.

You can use Vulert, which monitors open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can alert you in real-time. You can also check your application using the Vulert playground without signing up.

If immediate updates are not possible, consider removing the package from your project as a temporary measure until a secure version is available.

While specific exploits have not been detailed, the potential for data breaches and unauthorized access is significant due to the malicious communication.

Regularly check for updates from package maintainers, use tools like Vulert for monitoring, and subscribe to security advisories related to your dependencies.

How To Fix

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

npm uninstall mpesa-ui-components

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