Malicious Code Injection in tehah-kalian-bautka Package - npm Vulnerability

tehah-kalian-bautka Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168960: Malicious code in tehah-kalian-bautka (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 Penetration testing for web, API and mobile 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-kalian-bautka package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. The malicious nature of this package lies in its ability to modify essential files and republish variants, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from the package's malicious payload, which alters the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall tehah-kalian-bautka

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, avoid using the tehah-kalian-bautka package and consider using alternative packages that provide similar functionality without the associated risks. Always verify the integrity of packages before installation.

Conclusion

The tehah-kalian-bautka package poses a significant risk due to its malicious behavior of modifying and republishing npm packages. It is essential to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities in your dependencies.

See every vulnerability recorded for tehah-kalian-bautka →

Share this vulnerability

FAQ

Tehah-kalian-bautka is an npm package linked to a token reward campaign that has been identified as malicious due to its behavior of modifying and republishing packages.

The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising security and functionality.

You should uninstall the package immediately using the command: npm uninstall tehah-kalian-bautka.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just the package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

npm uninstall tehah-kalian-bautka

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