Malicious Code Injection in eoinreilly Package: npm Vulnerability Summary

eoinreilly Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171168: Malicious code in eoinreilly (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 eoinreilly package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate various functionalities within the npm registry but has been compromised to serve malicious purposes. It is primarily used for managing dependencies in JavaScript applications, but its integrity has been undermined by the introduction of harmful scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the eoinreilly package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to the automatic publication of derivative packages. The intent behind this is to inflate developer reputation scores for token rewards, ultimately polluting the npm registry and potentially compromising other applications that depend on these packages.

How To Fix

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

npm uninstall eoinreilly

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 eoinreilly package in your project. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The eoinreilly package has been identified as a vector for malicious code injection, posing significant risks to applications relying on it. It is crucial to remove this package and stay vigilant about the security of your dependencies. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for eoinreilly →

Share this vulnerability

FAQ

The eoinreilly package is an npm package that has been compromised to include malicious code, primarily associated with the tea.xyz token reward campaign.

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

You should remove the eoinreilly package from your project immediately and monitor for any updates or patches that may be released.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application using the Vulert playground without any signup.

Regularly audit your dependencies, use trusted sources for packages, and consider implementing automated tools to monitor for vulnerabilities.

How To Fix

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

npm uninstall eoinreilly

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