Malicious Code Injection in kamasada-nusata-bunjsadab Package

kamasada-nusata-bunjsadab Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157327: Malicious code in kamasada-nusata-bunjsadab (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

The kamasada-nusata-bunjsadab package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. However, it has been identified as containing malicious code that modifies essential files and repurposes the package for harmful activities.

Vulnerability Detail

The vulnerability originates from the package's malicious payload, which alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious scripts included in the package (auto.js, autopublish.js, etc.) are specifically designed to automate these harmful actions.

How To Fix

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

npm uninstall kamasada-nusata-bunjsadab

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, you can monitor your package dependencies using tools like Vulert. Vulert allows you to check for vulnerabilities in your application without needing to access the code or install additional software. You can use the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability.

Conclusion

The kamasada-nusata-bunjsadab package contains malicious code that poses a significant risk to developers and their projects. It is crucial to remove this package and monitor your dependencies to maintain the integrity of your applications.

See every vulnerability recorded for kamasada-nusata-bunjsadab →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation of derivative packages.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to the pollution of the npm registry.

You should uninstall the kamasada-nusata-bunjsadab package immediately using the command 'npm uninstall kamasada-nusata-bunjsadab'.

Yes, regularly monitor your dependencies using tools like Vulert and ensure you only use trusted packages.

There is no patch for this specific package; the recommended action is to uninstall it.

How To Fix

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

npm uninstall kamasada-nusata-bunjsadab

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