Malicious Code Injection in aoifemccarthy Package: npm Vulnerability Overview

aoifemccarthy Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170898: Malicious code in aoifemccarthy (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The aoifemccarthy package is part of the npm ecosystem, primarily used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign associated with the tea.xyz token reward initiative. This campaign has led to the proliferation of numerous derivative packages designed to manipulate developer reputation scores within the npm registry.

Vulnerability Detail

The vulnerability in the aoifemccarthy package stems from its involvement in a malicious campaign that generates and publishes derivative packages with randomized names. This behavior is executed through scripts that modify the package.json file, removing private flags, altering version numbers, and continuously republishing variants. The ramifications include potential pollution of the npm registry and manipulation of developer reputation metrics, which could lead to security risks and trust issues within the ecosystem.

How To Fix

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

npm uninstall aoifemccarthy

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 workaround, you can temporarily avoid using the aoifemccarthy package in your project. Additionally, you can monitor your dependencies using tools like Vulert, which analyzes your package-lock.json file to detect vulnerabilities in real-time.

Conclusion

The aoifemccarthy package has been identified as a malicious entity within the npm ecosystem, posing risks to developers and their projects. It is crucial to remove this package and monitor for any updates. Utilizing tools like Vulert can help maintain the security of your dependencies.

See every vulnerability recorded for aoifemccarthy →

Share this vulnerability

FAQ

The aoifemccarthy package is an npm package that has been identified as part of a malicious campaign targeting the npm registry.

This vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies.

You should remove the aoifemccarthy package from your project and monitor for any updates or patches that may address the vulnerability.

Yes, Vulert allows you to monitor and alert for open-source vulnerabilities in your software using just the package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall aoifemccarthy

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