Malicious Code Injection in tuti-tapai50-pore: A Threat to npm Users

tuti-tapai50-pore Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98429: Malicious code in tuti-tapai50-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package 'tuti-tapai50-pore' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior not only inflates developer reputation scores but also poses a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'tuti-tapai50-pore' stems from its malicious payload, which modifies the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, leading to pollution of the npm registry. This can result in developers inadvertently using compromised packages, exposing their applications to potential security risks.

How To Fix

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

npm uninstall tuti-tapai50-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 temporary workaround, you can avoid using the 'tuti-tapai50-pore' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file to alert you of any open-source vulnerabilities.

Conclusion

The 'tuti-tapai50-pore' package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to remove this package from their projects and monitor for similar vulnerabilities using tools like Vulert to ensure the security of their applications.

See every vulnerability recorded for tuti-tapai50-pore →

Share this vulnerability

FAQ

It is an npm package that has been identified as malicious, designed to manipulate the npm registry and inflate developer reputation scores.

If your application uses the 'tuti-tapai50-pore' package, it may inadvertently include malicious code that can compromise security and integrity.

You should immediately uninstall the package using 'npm uninstall tuti-tapai50-pore' and check your project for any other affected packages.

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

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 tuti-tapai50-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