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

ciaraflynn Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171042: Malicious code in ciaraflynn (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The ciaraflynn package is part of the npm ecosystem, primarily used for various JavaScript applications. It is often utilized in projects that require dependency management and package distribution. However, this package has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security concerns for developers and users alike.

Vulnerability Detail

The ciaraflynn package contains malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a larger scheme associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores by flooding the npm registry with derivative packages. The ramifications include potential exposure of sensitive data, unauthorized access to systems, and pollution of the npm registry with malicious packages.

How To Fix

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

npm uninstall ciaraflynn

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 measure, avoid using the ciaraflynn package and monitor your dependencies for any unauthorized changes. Regularly audit your npm packages using tools like npm audit to identify vulnerabilities.

Conclusion

The ciaraflynn package poses a significant security threat due to its malicious code designed to exploit npm's publishing system. Developers should take immediate action to remove this package and monitor their dependencies to ensure the integrity of their projects.

See every vulnerability recorded for ciaraflynn →

Share this vulnerability

FAQ

The ciaraflynn package is an npm package used in JavaScript applications, but it has been identified as malicious.

The malicious code can modify your package.json, remove private flags, and publish unauthorized packages, leading to security risks.

You should uninstall the ciaraflynn package immediately and check your project for any unauthorized changes.

You can use tools like npm audit or services like Vulert to monitor your project for open-source vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall ciaraflynn

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