Malicious Code Injection in kamasada-nutasai-aadsaffa Package

kamasada-nutasai-aadsaffa Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157359: Malicious code in kamasada-nutasai-aadsaffa (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The kamasada-nutasai-aadsaffa package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that seeks to exploit the npm registry by flooding it with derivative packages, ultimately harming developers and users alike.

Vulnerability Detail

The vulnerability stems from the package being associated with a malicious campaign that generates and publishes derivative packages with randomized names. This is executed through scripts that modify the package.json file to remove private flags, alter version numbers, and create numerous variants of the package. The ramifications include pollution of the npm registry, potential security risks for applications relying on this package, and damage to developer reputation scores due to the automated nature of the malicious activity.

How To Fix

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

npm uninstall kamasada-nutasai-aadsaffa

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 measure, you can avoid using the kamasada-nutasai-aadsaffa package entirely and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The kamasada-nutasai-aadsaffa package poses a significant risk due to its association with malicious activities aimed at manipulating the npm registry. It is essential for developers to be vigilant, remove this package, and utilize tools like Vulert to monitor their applications for vulnerabilities.

See every vulnerability recorded for kamasada-nutasai-aadsaffa →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to flood the npm registry with derivative packages.

Using this package can lead to security risks, including the potential for malicious code execution and pollution of your project's dependencies.

You should remove the kamasada-nutasai-aadsaffa package from your project and monitor for any updates or patches that may be released.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability 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-nutasai-aadsaffa

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