Malicious Code Injection in sunden-diak-n Package: npm Vulnerability Overview

sunden-diak-n Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166253: Malicious code in sunden-diak-n (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 sunden-diak-n package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol. However, the malicious nature of these packages poses significant risks to developers and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the sunden-diak-n package originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior can pollute the npm registry, making it difficult for developers to find legitimate packages and potentially exposing them to malicious code.

How To Fix

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

npm uninstall sunden-diak-n

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 monitor your project for any unauthorized changes to the package.json file and ensure that no untrusted packages are installed. Regularly audit your npm packages using the command 'npm audit' to identify potential vulnerabilities.

Conclusion

The sunden-diak-n package poses a significant risk due to its malicious code injection capabilities. It is crucial for developers to be aware of such vulnerabilities and take proactive measures to secure their projects. Regular audits and the use of monitoring tools like Vulert can help mitigate these risks.

See every vulnerability recorded for sunden-diak-n →

Share this vulnerability

FAQ

The sunden-diak-n package is part of a malicious campaign on npm that automates the creation and publication of derivative packages to inflate developer reputation scores.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

You should uninstall the sunden-diak-n package immediately using 'npm uninstall sunden-diak-n' and audit your project for any other vulnerabilities.

Regularly update your dependencies, use trusted packages, and utilize tools like Vulert to monitor your project for vulnerabilities.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check if your application is affected by vulnerabilities without any signup at the Vulert playground.

How To Fix

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

npm uninstall sunden-diak-n

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