Malicious Code Vulnerability in Aineflynn Package

aineflynn Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170738: Malicious code in aineflynn (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 Aineflynn package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often include scripts that manipulate package metadata and publish unauthorized derivatives, impacting the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the Aineflynn package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores for token rewards, leading to pollution of the npm registry and potential security risks for users relying on affected packages.

How To Fix

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

npm uninstall aineflynn

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, you can remove the Aineflynn package from your project by executing the following command: 'npm uninstall aineflynn'. This will prevent any malicious activities associated with the package until a fix is applied.

Conclusion

The Aineflynn package poses a significant security risk due to its malicious code that alters package metadata and publishes unauthorized derivatives. It is essential to take immediate action by updating or uninstalling the package to protect your project from potential threats.

See every vulnerability recorded for aineflynn →

Share this vulnerability

FAQ

Aineflynn is an npm package that has been linked to a malicious campaign aimed at manipulating package metadata and inflating developer reputation scores.

The vulnerability can lead to unauthorized modifications of your project's package.json file, potentially compromising the integrity of your application and exposing it to further security risks.

If you have installed Aineflynn, it is crucial to uninstall the package immediately and check for any other affected packages in your project.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time. Vulert uses package-lock.json to alert you to any issues without requiring code access.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall aineflynn

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