Malicious Code Injection in maman-enting30-apidev Package

maman-enting30-apidev Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-88208: Malicious code in maman-enting30-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 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 maman-enting30-apidev package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that manipulate developer reputation scores. This package, like others in its category, is designed to automatically generate and publish derivative packages, which can lead to significant pollution of the npm registry and compromise the integrity of the software supply chain.

Vulnerability Detail

The vulnerability in the maman-enting30-apidev package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which are often themed around Indonesian culture. This behavior is intended to inflate developer reputation scores by continuously republishing variants, thereby polluting the npm registry. The ramifications include potential security risks for developers who unknowingly install these malicious packages, as well as a degradation of trust in the npm ecosystem.

How To Fix

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

npm uninstall maman-enting30-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, you can avoid using the maman-enting30-apidev package altogether. If it is already installed, you can uninstall it using the following command: npm uninstall maman-enting30-apidev. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities without needing to access the code directly.

Conclusion

The maman-enting30-apidev package contains malicious code that poses a significant risk to developers and the integrity of the npm ecosystem. It is crucial to remove this package from your projects and utilize monitoring tools like Vulert to stay informed about potential vulnerabilities.

See every vulnerability recorded for maman-enting30-apidev →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, known for generating and publishing derivative packages.

The vulnerability can lead to the installation of malicious code, which may compromise your project's security and integrity.

You should uninstall the maman-enting30-apidev package immediately and monitor your project for any other vulnerabilities.

Using tools like Vulert can help monitor your project for open-source vulnerabilities in real-time, allowing you to take action before issues arise.

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 maman-enting30-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