Malicious Code Vulnerability in tomi-kupat33-pore Package

tomi-kupat33-pore Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98414: Malicious code in tomi-kupat33-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The tomi-kupat33-pore package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as malicious due to its capability to modify package metadata and republish variants, leading to potential registry pollution.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the tomi-kupat33-pore package, which includes scripts that alter the package.json file by removing private flags and changing version numbers. It generates random package names and continuously republishes these variants, which can lead to a polluted npm registry and compromise the integrity of the ecosystem. This behavior can mislead developers and users, potentially causing security risks and loss of trust in the package management system.

How To Fix

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

npm uninstall tomi-kupat33-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 tomi-kupat33-pore package altogether. If it is already included in your project, you can remove it using the command: npm uninstall tomi-kupat33-pore. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.

Conclusion

The tomi-kupat33-pore package poses a significant risk due to its malicious behavior of altering package metadata and republishing variants. It is crucial to remove this package from your projects and utilize monitoring tools like Vulert to stay informed about potential vulnerabilities.

See every vulnerability recorded for tomi-kupat33-pore →

Share this vulnerability

FAQ

The tomi-kupat33-pore package is an npm package linked to the tea.xyz token reward campaign, designed to automatically publish derivative packages.

This vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project and misleading developers.

You should uninstall the tomi-kupat33-pore package immediately and monitor your project for any other vulnerabilities.

Yes, you can use Vulert, which allows you to monitor and alert for open-source vulnerabilities in real-time using your package-lock.json file.

Regularly update your dependencies, use tools like Vulert for monitoring, and review package contents before installation.

How To Fix

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

npm uninstall tomi-kupat33-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