Malicious Code Injection in eamonflynn Package: npm Vulnerability Overview
Summary
MAL-2025-171121: Malicious code in eamonflynn (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The eamonflynn package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. The primary function of eamonflynn, like many npm packages, is to provide reusable code for developers, but its compromised nature poses significant risks to users and their projects.
Vulnerability Detail
The vulnerability in the eamonflynn package originates from its association with the tea.xyz token reward campaign. This campaign employs autopublish scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The malicious code continuously republishes these variants, leading to pollution of the npm registry and potential exploitation of developers' reputations. The ramifications include unauthorized access to sensitive data, increased risk of dependency confusion, and overall degradation of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall eamonflynnIf 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 eamonflynn package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can implement strict dependency management practices to monitor and control package installations.
Conclusion
The eamonflynn package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to remove this package and monitor their dependencies closely to maintain the integrity of their projects.
See every vulnerability recorded for eamonflynn →
FAQ
The eamonflynn package is an npm package used for JavaScript development, but it has been compromised to include malicious code.
The malicious code can modify your project's package.json, remove private flags, and publish unauthorized versions, potentially compromising your project's integrity.
You should immediately remove the eamonflynn package from your project and check for any unauthorized changes in your package.json file.
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.
