Malicious Code Injection in leonard-tea-archive: A Threat to npm Ecosystem

leonard-tea-archive Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105087: Malicious code in leonard-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 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 'leonard-tea-archive' package is part of a broader campaign associated with the tea.xyz token reward system. This package, like others in the campaign, is designed to manipulate the npm registry by automatically generating and publishing derivative packages. Its primary function is to inflate developer reputation scores for rewards, but it also poses significant risks to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability originates from the package's malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only pollutes the npm registry but also compromises the security and reliability of packages within the ecosystem, potentially leading to further exploitation.

How To Fix

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

npm uninstall leonard-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 measure, you can avoid using the 'leonard-tea-archive' package and monitor your project for any dependencies that may inadvertently include it. Regularly audit your package-lock.json file to identify and remove any malicious packages.

Conclusion

The 'leonard-tea-archive' package poses a significant risk to the npm ecosystem due to its malicious behavior. It is essential for developers to be vigilant about the packages they use, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for leonard-tea-archive →

Share this vulnerability

FAQ

It is a package associated with the tea.xyz token reward campaign, designed to manipulate npm registry by publishing derivative packages.

The malicious code can compromise your project's integrity by polluting the npm registry and potentially introducing security risks.

You should uninstall the package immediately using 'npm uninstall leonard-tea-archive' and audit your dependencies.

Regularly audit your dependencies, use trusted packages, and keep your software updated to the latest secure versions.

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 at Vulert Scanner without any signup.

How To Fix

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

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