Malicious Code Injection in eko-lepet50-remi: A Threat to npm Users

eko-lepet50-remi Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101958: Malicious code in eko-lepet50-remi (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

eko-lepet50-remi is an npm package that has been identified as part of a malicious campaign targeting developers. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish variants, leading to potential security risks for users.

Vulnerability Detail

The vulnerability in eko-lepet50-remi originates from its design to execute autopublish scripts that alter the package.json file by removing private flags and changing version numbers. This behavior allows the package to generate random names and continuously republish itself, polluting the npm registry. The ramifications include compromised developer reputations, potential exposure of sensitive information, and the risk of inadvertently using malicious packages in projects.

How To Fix

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

npm uninstall eko-lepet50-remi

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 remove the eko-lepet50-remi package from your project to prevent any malicious activity. Use the following command: npm uninstall eko-lepet50-remi. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The eko-lepet50-remi package poses a significant threat due to its malicious code designed to manipulate package files and republish itself. It is crucial for developers to take immediate action to remove this package and utilize tools like Vulert for ongoing monitoring of vulnerabilities in their projects.

See every vulnerability recorded for eko-lepet50-remi →

Share this vulnerability

FAQ

eko-lepet50-remi is an npm package involved in a malicious campaign that modifies package files and republishes itself under random names.

This vulnerability can lead to the inclusion of malicious code in your project, potentially compromising security and developer reputation.

You should immediately uninstall the eko-lepet50-remi package and monitor your project for any unusual behavior.

Yes, Vulert can monitor your package-lock.json for vulnerabilities in real-time, helping you stay informed about potential threats.

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

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 eko-lepet50-remi

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