Malicious Code Vulnerability in worldwide_emu_0xrequest Package

worldwide_emu_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-111000: Malicious code in worldwide_emu_0xrequest (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 worldwide_emu_0xrequest package 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, it has been identified as containing malicious code that compromises its integrity and the security of applications that depend on it.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the worldwide_emu_0xrequest package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The implications of this vulnerability include potential exposure of sensitive information, unauthorized access to systems, and the degradation of the npm ecosystem's reliability.

How To Fix

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

npm uninstall worldwide_emu_0xrequest

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 worldwide_emu_0xrequest package from your project by executing the command: 'npm uninstall worldwide_emu_0xrequest'. This will prevent the execution of any malicious code until a secure version is available.

Conclusion

The worldwide_emu_0xrequest package contains a serious vulnerability due to embedded malicious code that can compromise application security. It is crucial to update or remove the package to protect your application and maintain the integrity of the npm ecosystem.

See every vulnerability recorded for worldwide_emu_0xrequest →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.

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

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

You can temporarily uninstall the worldwide_emu_0xrequest package to mitigate the risk until a secure version is available.

Detailed information can be found in the vulnerability report and the npm registry, as well as through security advisories related to the package.

How To Fix

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

npm uninstall worldwide_emu_0xrequest

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