Malicious Code Injection in mahesa-bakso1-apidev Package

mahesa-bakso1-apidev Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-88114: Malicious code in mahesa-bakso1-apidev (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The mahesa-bakso1-apidev package is part of the npm ecosystem, often used for developing APIs. It is designed to facilitate the creation and management of backend services. However, this package has been identified as part of a malicious campaign that exploits npm's publishing features to inflate developer reputation scores through automated scripts.

Vulnerability Detail

The vulnerability stems from the package being associated with the tea.xyz token reward campaign, which floods npm with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The malicious payload continuously republishes variants, polluting the npm registry and potentially compromising the integrity of dependent applications.

How To Fix

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

npm uninstall mahesa-bakso1-apidev

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 workaround, consider using alternative packages that offer similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file to alert you in real-time about open-source vulnerabilities.

Conclusion

The mahesa-bakso1-apidev package has been identified as a vector for malicious code injection, posing significant risks to applications that utilize it. Immediate action is required to remove the package and monitor for any vulnerabilities using tools like Vulert.

See every vulnerability recorded for mahesa-bakso1-apidev →

Share this vulnerability

FAQ

mahesa-bakso1-apidev is an npm package used for developing APIs, but it has been compromised with malicious code.

The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your application's integrity and security.

You should uninstall the package immediately and consider using alternative packages that do not have known vulnerabilities.

You can use Vulert to monitor your package-lock.json file for vulnerabilities without needing to install any software.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall mahesa-bakso1-apidev

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