Malicious Code Injection in tehah-manda-konatol Package - npm Vulnerability

tehah-manda-konatol Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168977: Malicious code in tehah-manda-konatol (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 tehah-manda-konatol package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. This package is designed to interact with the npm registry, but it has been identified as containing malicious scripts that can manipulate package metadata and publish harmful variants. The primary functionality of this package is to generate and publish derivative packages, which can lead to reputation inflation for developers involved in the tea protocol.

Vulnerability Detail

The vulnerability originates from the presence of malicious code within the tehah-manda-konatol package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which can lead to the pollution of the npm registry. The malicious payload is designed to continuously republish these variants, potentially affecting the integrity of the npm ecosystem and compromising the security of applications that depend on this package.

How To Fix

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

npm uninstall tehah-manda-konatol

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 can avoid using the tehah-manda-konatol package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file using Vulert, which alerts you in real-time for open-source vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The tehah-manda-konatol package poses a significant risk due to its malicious code that can compromise the integrity of the npm registry and affect applications relying on it. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities to maintain the security of your projects.

See every vulnerability recorded for tehah-manda-konatol →

Share this vulnerability

FAQ

The tehah-manda-konatol package is part of a campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages.

The malicious code can modify your package.json file, leading to the removal of private flags and the introduction of potentially harmful package variants into your project.

You should uninstall the tehah-manda-konatol package immediately using 'npm uninstall tehah-manda-konatol' and check for any other affected packages.

Yes, you can use Vulert to monitor your package-lock.json file for open-source vulnerabilities in real-time without needing to access the code or install additional tools.

You can find detailed information about this vulnerability in the official GitHub repository or through vulnerability databases that track malicious packages.

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 tehah-manda-konatol

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