Malicious Code Injection in eoinmurphy Package: A Threat to npm Users

eoinmurphy Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171167: Malicious code in eoinmurphy (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 eoinmurphy package is part of the npm ecosystem, primarily used for JavaScript development. It is often leveraged by developers to manage dependencies and streamline the development process. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of numerous derivative packages with randomized names.

Vulnerability Detail

The vulnerability stems from the eoinmurphy package being associated with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of applications relying on this package. The malicious payload is designed to exploit the npm ecosystem by automating the creation of derivative packages, thereby posing a significant risk to developers and users alike.

How To Fix

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

npm uninstall eoinmurphy

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 eoinmurphy package and replace it with a trusted alternative. Additionally, you can use the following command to uninstall the package: npm uninstall eoinmurphy.

Conclusion

The eoinmurphy package poses a significant threat due to its malicious code that modifies package configurations and repopulates the npm registry with harmful variants. It is crucial for developers to take immediate action by removing this package and monitoring their applications for vulnerabilities.

See every vulnerability recorded for eoinmurphy →

Share this vulnerability

FAQ

The eoinmurphy package is a JavaScript package in the npm ecosystem, which has been identified as part of a malicious campaign.

This vulnerability can lead to the pollution of the npm registry and compromise the integrity of your application by introducing malicious code.

You should uninstall the eoinmurphy package immediately and monitor your application for any unusual behavior.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

npm uninstall eoinmurphy

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