Malicious Code Injection in eko-ronde62-remi Package - npm Vulnerability

eko-ronde62-remi Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101973: Malicious code in eko-ronde62-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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The eko-ronde62-remi package is part of a series of packages that emerged during the tea.xyz token reward campaign, which aimed to inflate developer reputation scores on npm. These packages are designed to automatically generate and publish derivative versions with randomized names, often leading to pollution of the npm registry. The malicious nature of this package lies in its ability to modify critical files, such as package.json, which can compromise the integrity of projects relying on it.

Vulnerability Detail

The vulnerability originates from the eko-ronde62-remi package, which contains scripts that remove private flags from package.json, alter version numbers, and generate random package names. This behavior allows the package to continuously republish variants, thereby polluting the npm registry and potentially affecting other projects. The malicious payload can lead to unauthorized access to sensitive information and disrupt the normal functioning of applications that depend on this package.

How To Fix

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

npm uninstall eko-ronde62-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 prevent the installation of the eko-ronde62-remi package by using npm's package-lock.json to monitor your dependencies. Ensure that your project does not include this package by checking your package.json and removing any references to it.

Conclusion

The eko-ronde62-remi package poses a significant risk due to its malicious code that modifies essential project files and repopulates the npm registry with unauthorized packages. It is crucial to remove this package and monitor your dependencies to maintain the security and integrity of your projects.

See every vulnerability recorded for eko-ronde62-remi →

Share this vulnerability

FAQ

The eko-ronde62-remi package is part of a malicious campaign that floods npm with packages designed to inflate developer reputation scores.

This vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your project's integrity and security.

You should uninstall the eko-ronde62-remi package immediately and check for any other affected packages in your project.

Yes, you can use Vulert to monitor your package-lock.json for open-source vulnerabilities in real-time without needing to access the code or install anything.

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 eko-ronde62-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