Malicious Code Injection in interior_emu_z3n Package: A Threat to npm Users

interior_emu_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95092: Malicious code in interior_emu_z3n (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The interior_emu_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, making them a significant threat to developers and users alike.

Vulnerability Detail

The vulnerability in the interior_emu_z3n package stems from its inclusion in a campaign that deploys malicious scripts (such as auto.js and autopublish.js) to alter package.json files. These scripts remove private flags, change version numbers, and generate random package names, leading to the pollution of the npm registry. This not only compromises the integrity of the affected packages but also poses a risk to developers who may unknowingly use these compromised packages in their projects.

How To Fix

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

npm uninstall interior_emu_z3n

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 interior_emu_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The interior_emu_z3n package poses a significant risk due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities. Staying informed and proactive is key to maintaining the security of your applications.

See every vulnerability recorded for interior_emu_z3n →

Share this vulnerability

FAQ

The interior_emu_z3n package is an npm package that is part of a malicious campaign aimed at manipulating package metadata for token rewards.

This vulnerability can lead to the inclusion of malicious code in your project, potentially compromising its security and integrity.

If you have installed the interior_emu_z3n package, you should uninstall it immediately using 'npm uninstall interior_emu_z3n'.

Yes, tools like Vulert can help monitor your project for open-source vulnerabilities in real-time using just the package-lock.json file.

You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner without needing to sign up.

How To Fix

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

npm uninstall interior_emu_z3n

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