Malicious Code Injection in dulameen Package - npm Vulnerability

dulameen Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171118: Malicious code in dulameen (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 dulameen package is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various applications to enhance functionality and streamline development processes. However, this package has been identified as part of a malicious campaign that aims to manipulate npm's registry by generating and publishing derivative packages with random names, ultimately inflating developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability stems from the dulameen package being involved in a malicious campaign linked to the tea.xyz token reward initiative. This package contains scripts designed to automatically generate and publish numerous derivative packages with randomized names, which can lead to the pollution of the npm registry. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, which can compromise the integrity of the npm ecosystem and potentially affect other dependent packages.

How To Fix

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

npm uninstall dulameen

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 dulameen package and replace it with a trusted alternative that provides similar functionality. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The dulameen package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and applications. It is essential to remove this package and replace it with trusted alternatives to maintain the integrity of your projects. Regular monitoring for vulnerabilities is also recommended.

See every vulnerability recorded for dulameen →

Share this vulnerability

FAQ

The dulameen package 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 the pollution of the npm registry, potentially affecting other packages and compromising the integrity of your application.

You should uninstall the dulameen package immediately using the command npm uninstall dulameen.

Yes, you should look for reputable packages that provide similar functionality and have a good track record in the community.

You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground at Vulert Scanner without any signup.

How To Fix

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

npm uninstall dulameen

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