Malicious Code Injection in tealove-boy38 Package: A Threat to npm Users

tealove-boy38 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168145: Malicious code in tealove-boy38 (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 tealove-boy38 package is part of a broader initiative associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. This package is designed to manipulate npm's ecosystem by generating and publishing derivative packages with randomized names. Its primary function is to inflate developer reputation scores in exchange for tea protocol token rewards, making it a target for malicious exploitation.

Vulnerability Detail

The vulnerability in the tealove-boy38 package stems from its malicious code that 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 to pollute the npm registry. This behavior can lead to a compromised development environment, where developers unknowingly install malicious packages, potentially exposing their applications to further vulnerabilities and security risks.

How To Fix

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

npm uninstall tealove-boy38

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 tealove-boy38 package and monitor your project for any unauthorized changes to your package.json file. Regularly audit your npm packages using 'npm audit' to identify and address vulnerabilities.

Conclusion

The tealove-boy38 package poses a significant risk to developers using npm due to its malicious code that alters package metadata and floods the registry with harmful derivatives. It is essential to remove this package and monitor your dependencies to maintain a secure development environment.

See every vulnerability recorded for tealove-boy38 →

Share this vulnerability

FAQ

Tealove-boy38 is an npm package associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores.

The vulnerability allows malicious code to modify your package.json file, potentially leading to the installation of harmful packages and compromising your project's security.

You should immediately uninstall the package using 'npm uninstall tealove-boy38' and audit your project for any other vulnerabilities.

Yes, you can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities in your software without requiring code access.

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 tealove-boy38

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