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

kapai-afaa-agda Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157425: Malicious code in kapai-afaa-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 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 package 'kapai-afaa-agda' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of this package appears to be generating and publishing derivative packages to inflate developer reputation scores for token rewards, making it a target for malicious exploitation.

Vulnerability Detail

The vulnerability in 'kapai-afaa-agda' originates from its design to include autopublish scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these malicious packages, potentially leading to security breaches and loss of data.

How To Fix

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

npm uninstall kapai-afaa-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 'kapai-afaa-agda' and any packages that depend on it. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'kapai-afaa-agda' package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be aware of such vulnerabilities and take proactive measures to secure their projects. Regularly updating dependencies and using monitoring tools like Vulert can help mitigate these risks.

See every vulnerability recorded for kapai-afaa-agda →

Share this vulnerability

FAQ

'kapai-afaa-agda' is an npm package associated with a token reward campaign that has been identified to contain malicious code.

The vulnerability can lead to the injection of malicious code into your project, potentially compromising security and data integrity.

You should remove 'kapai-afaa-agda' from your project and monitor for any updates or patches that may address the vulnerability.

You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time, alerting you to any issues.

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

How To Fix

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

npm uninstall kapai-afaa-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