Malicious Code Injection in elianerocha Package: npm Vulnerability Overview

elianerocha Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171137: Malicious code in elianerocha (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

The elianerocha package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised by the presence of autopublish scripts that generate and publish derivative packages with randomized names, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability in the elianerocha package stems from its association with malicious code designed to manipulate the package.json file. This code removes private flags, alters version numbers, and creates random package names, which can lead to the proliferation of unwanted packages in the npm registry. The origin of this vulnerability is traced back to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms to inflate developer reputations. The ramifications include potential security risks for developers who unknowingly install these malicious packages, as well as the degradation of the npm ecosystem's integrity.

How To Fix

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

npm uninstall elianerocha

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 elianerocha package and monitor your project's dependencies for any malicious activity. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The elianerocha package poses a significant risk due to its malicious code designed to manipulate npm's publishing system. Developers are advised to remove this package and utilize tools like Vulert for ongoing monitoring of their dependencies to safeguard against similar vulnerabilities in the future.

See every vulnerability recorded for elianerocha →

Share this vulnerability

FAQ

The elianerocha package is an npm package that has been identified as containing malicious code aimed at manipulating the npm registry.

This vulnerability can lead to the installation of unwanted packages, potentially compromising your project's security and integrity.

You should remove the elianerocha package from your project immediately and monitor your dependencies for any further vulnerabilities.

Yes, regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.

You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without requiring any signup.

How To Fix

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

npm uninstall elianerocha

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