Malicious Code Vulnerability in dtvomu-devapp: Exploitation of npm Registry

dtvomu-devapp Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101793: Malicious code in dtvomu-devapp (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 dtvomu-devapp package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the development of applications but has been compromised to include malicious scripts that manipulate its functionality. The vulnerability stems from the package's ability to modify its own metadata and republish itself under various names, which can lead to significant security risks for developers and users alike.

Vulnerability Detail

The vulnerability in dtvomu-devapp originates from its inclusion in a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that automatically alter the package.json file, removing private flags and changing version numbers. This behavior allows the package to generate random names and continuously republish itself, effectively polluting the npm registry. The ramifications include potential exposure of sensitive data, unauthorized access to systems, and a compromised development environment.

How To Fix

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

npm uninstall dtvomu-devapp

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 prevent the installation of the dtvomu-devapp package by adding it to your project's .npmrc file with the following line: package-lock=false. This will stop npm from installing this package until a secure version is available.

Conclusion

The dtvomu-devapp package has been identified as containing malicious code that can compromise the security of applications using it. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for dtvomu-devapp →

Share this vulnerability

FAQ

dtvomu-devapp is an npm package that was part of a token reward campaign but has been compromised to include malicious code.

The vulnerability can lead to unauthorized modifications of your application's dependencies, potentially exposing sensitive data and compromising security.

You should uninstall the package immediately using npm uninstall dtvomu-devapp and look for a secure alternative.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

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

npm uninstall dtvomu-devapp

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