Malicious Code Injection in Sunderan-Udiak-Vakaali Package

sunderan-udiak-vakaali Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166388: Malicious code in sunderan-udiak-vakaali (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

Sunderan-Udiak-Vakaali is an npm package that has been identified as part of a broader campaign to exploit the npm registry. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm ecosystem with malicious packages. The primary functionality of this package is to serve as a token reward mechanism, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in the Sunderan-Udiak-Vakaali package originates from its inclusion in a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious code modifies the package.json file by removing private flags, altering version numbers, and creating random package names, which leads to pollution of the npm registry. This can result in significant security risks, including unauthorized access to sensitive data and the potential for further exploitation of dependent applications.

How To Fix

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

npm uninstall sunderan-udiak-vakaali

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 Sunderan-Udiak-Vakaali package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which allows you to check for open-source vulnerabilities in your software without requiring code access or installation.

Conclusion

The Sunderan-Udiak-Vakaali package has been identified as a malicious entity within the npm ecosystem, posing significant risks to applications that utilize it. Immediate action is required to remove the package and safeguard your application from potential exploitation. Utilizing tools like Vulert can help maintain the security of your software by monitoring for vulnerabilities effectively.

See every vulnerability recorded for sunderan-udiak-vakaali →

Share this vulnerability

FAQ

It is an npm package that has been compromised as part of a malicious campaign targeting the npm registry.

The malicious code modifies package metadata, potentially leading to unauthorized access and further exploitation of your application.

You should uninstall the package immediately and monitor your application for any signs of compromise.

You can use Vulert to monitor your project for open-source vulnerabilities in real-time using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.

How To Fix

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

npm uninstall sunderan-udiak-vakaali

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