Malicious Code Injection in Kamasada Nusata Bujab Package

kamasada-nusata-bujab Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157319: Malicious code in kamasada-nusata-bujab (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Kamasada Nusata Bujab is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify essential files and republish variants, thereby polluting the npm ecosystem.

Vulnerability Detail

The vulnerability in the Kamasada Nusata Bujab package stems from its inclusion in a broader malicious campaign that utilizes autopublish scripts to create and disseminate numerous derivative packages with randomized names. This behavior not only compromises the integrity of the npm registry but also poses significant risks to developers who may unknowingly install these malicious packages. The payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, leading to potential security breaches and reputational damage for developers.

How To Fix

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

npm uninstall kamasada-nusata-bujab

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 Kamasada Nusata Bujab package and any other packages that may be part of the malicious campaign. Instead, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The Kamasada Nusata Bujab package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their projects. It is essential to take immediate action by uninstalling the package and monitoring your dependencies for vulnerabilities. Utilizing tools like Vulert can help ensure the security of your open-source projects.

See every vulnerability recorded for kamasada-nusata-bujab →

Share this vulnerability

FAQ

It is an npm package identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the installation of malicious code, compromising your project's security and potentially damaging your reputation as a developer.

You should uninstall the Kamasada Nusata Bujab package immediately and review your project's dependencies for any other potentially malicious packages.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.

Yes, consider using well-established and reputable npm packages that provide similar functionality without the associated risks of malicious behavior.

How To Fix

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

npm uninstall kamasada-nusata-bujab

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