Malicious Code Injection in nlelci-devapptea: A Threat to npm Ecosystem

nlelci-devapptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106353: Malicious code in nlelci-devapptea (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

nlelci-devapptea is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate token rewards through various automated scripts. However, this package has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with derivative packages, thereby compromising the integrity of the ecosystem.

Vulnerability Detail

The vulnerability in nlelci-devapptea stems from its inclusion in a campaign that deploys malicious scripts (auto.js, autopublish.js, etc.) to alter package.json files. These scripts remove private flags, change version numbers, and generate random package names, leading to the pollution of the npm registry. This not only affects the reputation of legitimate developers but also poses a risk of dependency confusion and potential exploitation of applications relying on these packages.

How To Fix

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

npm uninstall nlelci-devapptea

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 avoid using the nlelci-devapptea package and monitor your package-lock.json file for any unauthorized changes. Regularly audit your dependencies using npm audit to identify and address vulnerabilities.

Conclusion

The nlelci-devapptea package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package and monitor your dependencies to maintain the security of your applications.

See every vulnerability recorded for nlelci-devapptea →

Share this vulnerability

FAQ

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

The malicious code modifies package metadata, potentially leading to dependency confusion and the introduction of insecure packages into your application.

You should uninstall the package immediately using the command 'npm uninstall nlelci-devapptea' and audit your project for any other vulnerabilities.

You can use tools like npm audit to check for vulnerabilities in your dependencies. Additionally, Vulert can help monitor your package-lock.json for real-time alerts on open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall nlelci-devapptea

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