Malicious Code Injection in sunden-diak-nulamn: A Threat to npm Ecosystem

sunden-diak-nulamn Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166273: Malicious code in sunden-diak-nulamn (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'sunden-diak-nulamn' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, its functionality has been compromised, making it a vector for malicious activities.

Vulnerability Detail

The vulnerability in 'sunden-diak-nulamn' originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to reputation damage for developers and can clutter the npm ecosystem with unwanted packages.

How To Fix

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

npm uninstall sunden-diak-nulamn

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 an immediate workaround, you can remove the 'sunden-diak-nulamn' package from your project by executing: npm uninstall sunden-diak-nulamn. This will prevent any malicious code from executing in your environment until a secure version is available.

Conclusion

The 'sunden-diak-nulamn' package poses a significant threat due to its malicious code that alters package configurations and floods the npm registry. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications and maintain the integrity of the npm ecosystem.

See every vulnerability recorded for sunden-diak-nulamn →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json files and repackages them under random names, leading to npm registry pollution.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

The risks include potential reputation damage for developers, cluttering of the npm registry, and possible security breaches due to the execution of malicious code.

Check the npm registry for any updates to the 'sunden-diak-nulamn' package that may address this vulnerability.

As a temporary measure, uninstall the package to prevent any malicious activity until a secure version is released.

How To Fix

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

npm uninstall sunden-diak-nulamn

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