Malicious Code Injection in selected_opossum_z3n Package

selected_opossum_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96497: Malicious code in selected_opossum_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 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 selected_opossum_z3n package is part of the npm ecosystem and has been identified as part of a token reward campaign associated with tea.xyz. This package is designed to facilitate the automatic generation and publishing of derivative packages, which can inflate developer reputation scores in exchange for token rewards. However, it has been compromised to include malicious scripts that can alter package configurations and publish unwanted variants.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the selected_opossum_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to pollution of the npm registry. The malicious payload is designed to continuously republish these variants, potentially harming the integrity of the npm ecosystem and affecting developers' ability to manage their packages effectively.

How To Fix

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

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

Conclusion

The selected_opossum_z3n package has been identified as containing malicious code that can compromise the integrity of your npm projects. It is crucial to take immediate action by updating or uninstalling the package to safeguard your application. Utilize tools like Vulert for ongoing monitoring of vulnerabilities in your dependencies.

See every vulnerability recorded for selected_opossum_z3n →

Share this vulnerability

FAQ

The selected_opossum_z3n package is an npm package that is part of a token reward campaign, designed to automate the generation and publishing of derivative packages.

The malicious code can alter your package.json file, remove private flags, and publish unwanted package variants, which can compromise the integrity of your project and the npm registry.

Yes, you can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. You can check if your application is affected by visiting the Vulert playground at Vulert Scanner.

If you cannot update the package right away, it is advisable to uninstall the selected_opossum_z3n package to prevent any potential exploitation of the vulnerability.

To prevent similar vulnerabilities, regularly update your dependencies, monitor for security advisories, and utilize tools like Vulert to keep track of vulnerabilities in your open-source packages.

How To Fix

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

npm uninstall selected_opossum_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