Malicious Code Detected in eko-bakwan77-ruro: A Threat to npm Users

eko-bakwan77-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101939: Malicious code in eko-bakwan77-ruro (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 package eko-bakwan77-ruro is part of a broader campaign targeting npm users, leveraging the tea.xyz token reward system. This package is designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names, ultimately aimed at inflating developer reputation scores. Its malicious nature poses a significant risk to developers and users relying on npm for package management.

Vulnerability Detail

The vulnerability in eko-bakwan77-ruro originates from its involvement in a token reward campaign that floods the npm registry with malicious packages. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages.

How To Fix

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

npm uninstall eko-bakwan77-ruro

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 eko-bakwan77-ruro package and any other packages associated with the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to keep track of vulnerabilities in your dependencies.

Conclusion

The eko-bakwan77-ruro package poses a significant threat to npm users due to its malicious behavior aimed at manipulating the npm registry. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain the security and integrity of your projects.

See every vulnerability recorded for eko-bakwan77-ruro →

Share this vulnerability

FAQ

eko-bakwan77-ruro is an npm package that has been identified as malicious, part of a campaign to manipulate the npm registry for token rewards.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project's dependencies and exposing you to security risks.

If you have installed eko-bakwan77-ruro, you should uninstall it immediately using 'npm uninstall eko-bakwan77-ruro' and check your project for any other affected packages.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

Yes, 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-bakwan77-ruro

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