Malicious Code Injection in kapai-afamnaa-agda: A Threat to npm Users

kapai-afamnaa-agda Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157431: Malicious code in kapai-afamnaa-agda (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 package 'kapai-afamnaa-agda' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior raises significant concerns regarding the integrity and security of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'kapai-afamnaa-agda' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants that pollute the npm registry, potentially leading to reputation damage for developers and security risks for users who unknowingly install these compromised packages.

How To Fix

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

npm uninstall kapai-afamnaa-agda

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 'kapai-afamnaa-agda' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package dependencies for vulnerabilities.

Conclusion

The 'kapai-afamnaa-agda' package poses a significant threat due to its malicious behavior, which can compromise the integrity of the npm ecosystem. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities using tools like Vulert to maintain secure applications.

See every vulnerability recorded for kapai-afamnaa-agda →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that modifies package.json files and publishes variants to pollute the npm registry.

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

If you have installed this package, you should uninstall it immediately using 'npm uninstall kapai-afamnaa-agda' and look for alternatives.

While specific alternatives depend on your use case, consider searching the npm registry for similar packages that do not have known vulnerabilities.

Vulert monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json, ensuring you stay informed about potential risks.

How To Fix

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

npm uninstall kapai-afamnaa-agda

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