Malicious Code Injection in kamasada-natib-yal: A Threat to npm Ecosystem

kamasada-natib-yal Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157276: Malicious code in kamasada-natib-yal (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 package 'kamasada-natib-yal' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, notorious for flooding the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to users and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'kamasada-natib-yal' originates from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of applications that depend on these packages. The malicious payload can also lead to unauthorized access and manipulation of user data.

How To Fix

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

npm uninstall kamasada-natib-yal

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 use the following command to prevent the installation of known malicious packages: 'npm audit fix'. This command will attempt to automatically fix vulnerabilities in your dependencies, but it is crucial to monitor your package dependencies regularly.

Conclusion

The 'kamasada-natib-yal' package poses a significant threat to the npm ecosystem due to its malicious behavior. Users are advised to uninstall this package and monitor their dependencies closely. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities in real-time.

See every vulnerability recorded for kamasada-natib-yal →

Share this vulnerability

FAQ

'kamasada-natib-yal' is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

This vulnerability can lead to unauthorized modifications of your application's dependencies, potentially compromising its security and functionality.

You should uninstall the package immediately using 'npm uninstall kamasada-natib-yal' and check your package-lock.json for any references to it.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json. You can also check your application against known vulnerabilities using the Vulert playground.

There is no patch for 'kamasada-natib-yal' as it is recommended to remove the package entirely due to its malicious nature.

How To Fix

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

npm uninstall kamasada-natib-yal

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