Malicious Code Injection in tuti-nasipecel29-wekto: A Threat to npm Ecosystem

tuti-nasipecel29-wekto Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-91294: Malicious code in tuti-nasipecel29-wekto (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-nasipecel29-wekto is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The functionality of this package is compromised due to malicious code that modifies essential files, leading to potential security risks.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the tuti-nasipecel29-wekto package. This payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. The continuous republishing of these variants pollutes the npm registry, posing a risk to developers and users who may unknowingly install these compromised packages. The ramifications include potential exposure to further malicious activities and a degradation of the npm ecosystem's integrity.

How To Fix

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

npm uninstall tuti-nasipecel29-wekto

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 tuti-nasipecel29-wekto package and refrain from installing any packages that appear to be part of the tea.xyz token reward campaign. Monitor your project for any unauthorized changes to package.json and other critical files.

Conclusion

The tuti-nasipecel29-wekto package poses a significant security risk due to its malicious code that alters critical files and pollutes the npm registry. It is essential to remove this package and monitor your projects for any unauthorized changes. Utilizing tools like Vulert can help maintain the security of your open-source dependencies.

See every vulnerability recorded for tuti-nasipecel29-wekto →

Share this vulnerability

FAQ

The impact includes potential exposure to malicious code, which can lead to unauthorized access and manipulation of your project.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Immediately uninstall the package using npm uninstall tuti-nasipecel29-wekto and review your project for any unauthorized changes.

Currently, there are no patches available for the tuti-nasipecel29-wekto package. The best course of action is to remove it entirely.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about the latest security advisories in the npm ecosystem.

How To Fix

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

npm uninstall tuti-nasipecel29-wekto

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