Malicious Code Injection in kapai-safa-agada Package

kapai-safa-agada Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157433: Malicious code in kapai-safa-agada (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 kapai-safa-agada package is part of the npm ecosystem, which is widely used for JavaScript development. 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 is to facilitate token rewards, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in the kapai-safa-agada package originates from its association with a malicious campaign designed to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This not only pollutes the npm registry but also poses a significant risk to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall kapai-safa-agada

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-safa-agada package altogether until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The kapai-safa-agada package has been identified as containing malicious code that can compromise the security of applications using it. It is crucial for developers to stay informed about such vulnerabilities and take appropriate actions to secure their projects. Regular updates and monitoring tools like Vulert can help maintain the integrity of your software.

See every vulnerability recorded for kapai-safa-agada →

Share this vulnerability

FAQ

The kapai-safa-agada package is an npm package involved in the tea.xyz token reward campaign, which has been compromised to include malicious code.

The malicious code modifies your package.json file, potentially leading to security vulnerabilities and the pollution of the npm registry with harmful packages.

If you have installed the kapai-safa-agada package, you should update it to the latest version or remove it from your project to mitigate any risks.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities in your software.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall kapai-safa-agada

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