Malicious Code Injection in rodrick-tea-archive: A Threat to npm Users

rodrick-tea-archive Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108183: Malicious code in rodrick-tea-archive (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

rodrick-tea-archive is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the distribution of token rewards through various scripts. However, it has been identified as a malicious package that modifies its own metadata and publishes numerous derivative packages to manipulate developer reputation scores.

Vulnerability Detail

The vulnerability in rodrick-tea-archive stems from its malicious code that alters the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to clutter the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly install these malicious packages.

How To Fix

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

npm uninstall rodrick-tea-archive

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, avoid using the rodrick-tea-archive package and monitor your project's dependencies for any unauthorized changes. Regularly audit your npm packages using 'npm audit' to identify and address vulnerabilities.

Conclusion

The rodrick-tea-archive package poses a significant threat due to its malicious behavior of modifying package metadata and flooding the npm registry with harmful derivatives. It is essential for developers to remove this package and monitor their dependencies for security.

See every vulnerability recorded for rodrick-tea-archive →

Share this vulnerability

FAQ

rodrick-tea-archive is an npm package associated with the tea.xyz token reward campaign, which has been identified as malicious.

The vulnerability can lead to the installation of malicious packages that may compromise your project's integrity and security.

You should uninstall the package immediately using 'npm uninstall rodrick-tea-archive' and audit your project for any other vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access.

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 rodrick-tea-archive

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