Malicious Code Injection in dual_emu-silentdev Package

dual_emu-silentdev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101795: Malicious code in dual_emu-silentdev (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 dual_emu-silentdev package is part of the npm ecosystem, which is widely used for JavaScript development. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of this package is to facilitate certain development tasks, but it has been compromised to serve malicious purposes.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the dual_emu-silentdev package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names that are often themed around Indonesian culture. The intent behind this is to inflate developer reputation scores for token rewards by continuously republishing these variants, thereby polluting the npm registry. The ramifications of this vulnerability include potential exposure of sensitive data, unauthorized access to systems, and degradation of the npm ecosystem's integrity.

How To Fix

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

npm uninstall dual_emu-silentdev

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 remove the dual_emu-silentdev package from your project by executing the following command: npm uninstall dual_emu-silentdev. This will prevent any malicious code from executing while you seek a secure alternative.

Conclusion

The dual_emu-silentdev package has been identified as containing malicious code that compromises the integrity of the npm ecosystem. It is essential for developers to be vigilant and take immediate action to remove this package and monitor their projects for vulnerabilities.

See every vulnerability recorded for dual_emu-silentdev →

Share this vulnerability

FAQ

The dual_emu-silentdev package is an npm package that has been compromised to include malicious code aimed at inflating developer reputation scores.

The malicious code can modify your package.json file, potentially exposing sensitive information and leading to unauthorized actions within your project.

If you have installed the dual_emu-silentdev package, it is crucial to uninstall it immediately and check for any unauthorized changes in your project.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without signing up.

Detailed information about this vulnerability can be found in the Open Source Vulnerability database or by consulting the npm registry for updates.

How To Fix

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

npm uninstall dual_emu-silentdev

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