Malicious Code Injection in patterson-tea-archive: npm Package Vulnerability

patterson-tea-archive Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106991: Malicious code in patterson-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The patterson-tea-archive package is part of the tea.xyz token reward campaign, which has been associated with a surge of malicious npm packages. These packages are designed to inflate developer reputation scores through the automatic generation and publication of derivative packages. The functionality of patterson-tea-archive is compromised by malicious scripts that alter package metadata and republish variants to the npm registry.

Vulnerability Detail

The vulnerability originates from malicious code embedded in the patterson-tea-archive package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names. The result is a pollution of the npm registry with potentially harmful packages, which can lead to security risks for developers and users relying on this package.

How To Fix

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

npm uninstall patterson-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, you can manually remove the patterson-tea-archive package from your project by running: npm uninstall patterson-tea-archive. Additionally, monitor your package-lock.json file for any unauthorized changes.

Conclusion

The patterson-tea-archive package contains malicious code that compromises the integrity of your project. It is crucial to remove this package and monitor your dependencies for any unauthorized changes. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities in the future.

See every vulnerability recorded for patterson-tea-archive →

Share this vulnerability

FAQ

The patterson-tea-archive package is part of a campaign that generates and publishes npm packages to inflate developer reputation scores.

The malicious code modifies your package.json, removes private flags, and can lead to the publication of unauthorized packages, posing security risks.

You should uninstall the patterson-tea-archive package immediately and monitor your project for any unauthorized changes.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Regularly audit your dependencies, use tools like Vulert to monitor vulnerabilities, and stay updated with the latest security patches for your packages.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall patterson-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