Malicious Code Injection in kamasada-nusta-buaiibdaan Package

kamasada-nusta-buaiibdaan Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157335: Malicious code in kamasada-nusta-buaiibdaan (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The kamasada-nusta-buaiibdaan package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package, like others in the campaign, is designed to manipulate npm's publishing system by generating and publishing derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, but this comes at the cost of security and integrity within the npm registry.

Vulnerability Detail

The vulnerability in the kamasada-nusta-buaiibdaan package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which floods the npm registry with these malicious packages. The ramifications include potential pollution of the npm registry, loss of developer reputation integrity, and exposure of users to untrusted code.

How To Fix

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

npm uninstall kamasada-nusta-buaiibdaan

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 workaround, consider using a package-lock.json file to monitor your dependencies. This file helps ensure that you are using the intended versions of packages and can prevent the installation of malicious packages. You can also utilize tools like Vulert to monitor and alert you in real-time for open-source vulnerabilities in your software.

Conclusion

The kamasada-nusta-buaiibdaan package contains malicious code that poses a significant risk to developers and their projects. It is crucial to uninstall this package and monitor your dependencies to maintain the integrity of your software. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for kamasada-nusta-buaiibdaan →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to manipulate npm's publishing system.

The vulnerability can lead to the pollution of the npm registry and expose your project to untrusted code, potentially compromising security.

You should uninstall the kamasada-nusta-buaiibdaan package immediately and monitor your dependencies for any malicious activity.

Yes, by using tools like Vulert, which monitors your package-lock.json for vulnerabilities, you can receive alerts in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall kamasada-nusta-buaiibdaan

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