Malicious Code Injection in sunden-diak-nul Package: A Threat to npm Users

sunden-diak-nul Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166264: Malicious code in sunden-diak-nul (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 sunden-diak-nul package is part of a broader campaign targeting npm users, where malicious packages are created to inflate developer reputation scores through automated scripts. These scripts generate and publish numerous derivative packages with altered names and configurations, posing a significant risk to the integrity of the npm registry and its users.

Vulnerability Detail

The vulnerability in the sunden-diak-nul package stems from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the security of applications relying on these packages. The malicious payload can potentially allow unauthorized access to sensitive data or disrupt application functionality.

How To Fix

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

npm uninstall sunden-diak-nul

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 sunden-diak-nul package and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The sunden-diak-nul package poses a significant risk due to its malicious code designed to manipulate npm registry data. Users are advised to uninstall this package and monitor their projects for vulnerabilities using tools like Vulert to ensure ongoing security.

See every vulnerability recorded for sunden-diak-nul →

Share this vulnerability

FAQ

The sunden-diak-nul package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.

The malicious code can modify your package.json file, remove private flags, and continuously republish variants, potentially compromising your application's security and integrity.

If you have installed the sunden-diak-nul package, you should uninstall it immediately using the command npm uninstall sunden-diak-nul and check for any dependencies that may rely on it.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application using the Vulert playground at Vulert Scanner.

There are no patches available for the sunden-diak-nul package as it is recommended to remove it entirely from your project.

How To Fix

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

npm uninstall sunden-diak-nul

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