Malicious Code Injection in kamasada-nusata-buajidibdan Package

kamasada-nusata-buajidibdan Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157317: Malicious code in kamasada-nusata-buajidibdan (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 kamasada-nusata-buajidibdan package is part of the npm ecosystem, often used in JavaScript projects for various functionalities. However, this package has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the kamasada-nusata-buajidibdan package, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names and continuously republishes these variants, polluting the npm registry. This can lead to compromised applications, as developers may unknowingly include these malicious packages in their projects, exposing them to potential attacks.

How To Fix

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

npm uninstall kamasada-nusata-buajidibdan

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-buajidibdan package and any of its derivatives. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The kamasada-nusata-buajidibdan package poses a significant security risk due to its malicious nature. Developers are advised to remove this package and monitor their dependencies closely. Utilizing tools like Vulert can help in maintaining the security of your applications.

See every vulnerability recorded for kamasada-nusata-buajidibdan →

Share this vulnerability

FAQ

It is an npm package identified as part of a malicious campaign that floods the npm registry with harmful derivatives.

Including this package can lead to security breaches, as it modifies your project's configuration and can introduce other malicious code.

Immediately remove the kamasada-nusata-buajidibdan package from your project and check for any other affected packages.

Yes, Vulert can monitor your package-lock.json for vulnerabilities without requiring code access or installation.

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 kamasada-nusata-buajidibdan

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