Malicious Code Exploit in udin-tahu59-pore Package: npm Vulnerability Overview

udin-tahu59-pore Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98441: Malicious code in udin-tahu59-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 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 udin-tahu59-pore package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol.

Vulnerability Detail

The vulnerability originates from the package's malicious code, which modifies the package.json file to remove private flags, alters version numbers, and creates random package names. This leads to the continuous republishing of variants, effectively polluting the npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as well as damage to the integrity of the npm ecosystem.

How To Fix

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

npm uninstall udin-tahu59-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 workaround, you can avoid using the udin-tahu59-pore package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.

Conclusion

The udin-tahu59-pore package poses a significant risk due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities using tools like Vulert.

See every vulnerability recorded for udin-tahu59-pore →

Share this vulnerability

FAQ

The udin-tahu59-pore package is an npm package involved in a malicious campaign to inflate developer reputation scores through the creation of numerous derivative packages.

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

You should remove the udin-tahu59-pore package from your project immediately and monitor your dependencies for any other vulnerabilities.

Yes, tools like Vulert can help monitor your open-source dependencies for vulnerabilities in real-time without requiring code access.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall udin-tahu59-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