Malicious Code Injection in ita-50 Package: A Threat to npm Ecosystem

ita-50 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156968: Malicious code in ita-50 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The ita-50 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of such packages is to manipulate developer reputation scores through automated publishing scripts, which can lead to significant risks within the ecosystem.

Vulnerability Detail

The vulnerability in the ita-50 package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which are then continuously republished to pollute the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages. The ramifications include potential security risks for developers who unknowingly use these packages, as well as the degradation of the npm registry's integrity.

How To Fix

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

npm uninstall ita-50

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, you can avoid using the ita-50 package altogether. If it is already included in your project, consider removing it with the command: npm uninstall ita-50. Additionally, you can monitor your package-lock.json file for any unauthorized changes.

Conclusion

The ita-50 package poses a significant threat due to its malicious code that alters package metadata and pollutes the npm registry. It is essential for developers to be vigilant, update their packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for ita-50 →

Share this vulnerability

FAQ

The ita-50 package is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.

The malicious code modifies your package.json file, potentially exposing your project to security risks and affecting the integrity of the npm registry.

If you have installed ita-50, you should uninstall it immediately using the command npm uninstall ita-50 and check for any unauthorized changes in your project.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities without any signup at the Vulert playground.

Regularly update your packages, monitor for vulnerabilities using tools like Vulert, and review the package's source and reputation before installation.

How To Fix

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

npm uninstall ita-50

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