Malicious Code Injection in clodaghmoran Package: npm Vulnerability Overview

clodaghmoran Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171046: Malicious code in clodaghmoran (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 clodaghmoran package is part of the npm ecosystem, often utilized for various JavaScript applications. It is designed to facilitate package management and distribution within Node.js environments. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages.

Vulnerability Detail

The vulnerability in the clodaghmoran package stems from its association with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the pollution of the npm registry and can compromise the integrity of applications relying on these packages. The malicious payload is designed to continuously republish variants, exacerbating the issue.

How To Fix

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

npm uninstall clodaghmoran

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 clodaghmoran package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The clodaghmoran package poses a significant risk due to its malicious code that alters package management files and floods the npm registry. It is essential to uninstall this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for clodaghmoran →

Share this vulnerability

FAQ

The clodaghmoran package is an npm package used in JavaScript applications, but it has been identified as part of a malicious campaign.

The malicious code can modify your package.json file, remove private flags, and publish unwanted packages, potentially compromising your application's integrity.

You should uninstall the clodaghmoran package immediately using the command: npm uninstall clodaghmoran.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by visiting the Vulert playground at Vulert Scanner.

Yes, you should look for alternative packages that provide similar functionality without the associated risks. Always check the package's reputation before use.

How To Fix

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

npm uninstall clodaghmoran

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