Malicious Code Injection in tehah-nutay-kob Package - npm Vulnerability

tehah-nutay-kob Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169040: Malicious code in tehah-nutay-kob (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 tehah-nutay-kob package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and continuously republish variants, leading to potential pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from malicious code embedded within the tehah-nutay-kob package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the proliferation of unwanted packages in the npm registry. The continuous republishing of these variants can confuse developers and compromise the integrity of the npm ecosystem, potentially leading to security risks and reputation damage for legitimate developers.

How To Fix

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

npm uninstall tehah-nutay-kob

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 a package-lock.json file to monitor your dependencies. This file can help you identify and prevent the installation of malicious packages. Additionally, you can utilize tools like Vulert to monitor and alert you in real-time for open-source vulnerabilities in your software. 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-nutay-kob package poses a significant risk due to its malicious code that modifies critical files and floods the npm registry with unwanted packages. It is crucial for developers to remove this package and utilize monitoring tools to safeguard their projects against similar vulnerabilities in the future.

See every vulnerability recorded for tehah-nutay-kob →

Share this vulnerability

FAQ

The tehah-nutay-kob package is part of a campaign that aims to inflate developer reputation scores by flooding the npm registry with numerous derivative packages.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to confusion and potential security risks.

You should uninstall the package immediately using the command: npm uninstall tehah-nutay-kob.

Yes, using a package-lock.json file and monitoring tools like Vulert can help you identify and prevent the installation of malicious packages.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall tehah-nutay-kob

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