Malicious Code Injection in mahesa-empal8-pore: A Threat to npm Ecosystem

mahesa-empal8-pore Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98094: Malicious code in mahesa-empal8-pore (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package 'mahesa-empal8-pore' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant security risk.

Vulnerability Detail

The vulnerability in 'mahesa-empal8-pore' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially leading to unauthorized access or exploitation of affected systems.

How To Fix

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

npm uninstall mahesa-empal8-pore

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 measure, you can avoid using the 'mahesa-empal8-pore' package and monitor your dependencies for any similar malicious packages. Regularly audit your npm packages using 'npm audit' to identify vulnerabilities.

Conclusion

The 'mahesa-empal8-pore' package poses a significant threat to the npm ecosystem due to its malicious code. It is crucial for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for mahesa-empal8-pore →

Share this vulnerability

FAQ

The main issue is that it contains malicious code designed to manipulate the npm registry and inflate developer reputation scores.

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

You should uninstall the package immediately using 'npm uninstall mahesa-empal8-pore' and check for any other affected packages.

While specific exploits have not been detailed, the malicious behavior of the package can lead to unauthorized access and manipulation of your npm environment.

Regularly audit your npm packages, keep your dependencies updated, and monitor for any new vulnerabilities using tools like Vulert.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall mahesa-empal8-pore

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