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

conormccarthy Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171057: Malicious code in conormccarthy (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 conormccarthy package is part of the npm ecosystem, which is widely used for JavaScript development. This package is implicated in a malicious campaign that aims to exploit npm's publishing system. It is designed to automatically generate and publish derivative packages, potentially compromising the integrity of the npm registry and affecting developers' reputations.

Vulnerability Detail

The vulnerability originates from the conormccarthy package, which is associated with the tea.xyz token reward campaign. This package contains scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names. The malicious payload continuously republishes these variants, polluting the npm registry and inflating developer reputation scores fraudulently. This poses significant risks, including the potential for code injection, reputation damage, and the spread of malicious software within the developer community.

How To Fix

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

npm uninstall conormccarthy

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 remove the conormccarthy package from your project by executing: npm uninstall conormccarthy. This will prevent any malicious code from executing while you assess the situation.

Conclusion

The conormccarthy package poses a significant threat due to its malicious code designed to exploit the npm registry. It is essential for developers to take immediate action by uninstalling the package and monitoring their projects for vulnerabilities. Utilizing tools like Vulert can enhance security and provide real-time alerts for potential threats.

See every vulnerability recorded for conormccarthy →

Share this vulnerability

FAQ

The conormccarthy package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

This vulnerability can lead to code injection, reputation damage, and the proliferation of malicious software, compromising your project's integrity.

You should immediately uninstall the conormccarthy package and check for any updates or patches that may address the vulnerability.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check your application against known vulnerabilities using the Vulert playground.

Regularly updating your dependencies, using tools like Vulert for monitoring, and auditing your packages can help prevent vulnerabilities.

How To Fix

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

npm uninstall conormccarthy

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