Malicious Code Injection in weak_clam_z3n Package

weak_clam_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97326: Malicious code in weak_clam_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 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 weak_clam_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate token rewards through the generation and publication of derivative packages. However, this package has been identified as containing malicious code that compromises its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability in the weak_clam_z3n package stems from its malicious payload that modifies the package.json file. This payload removes private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The origin of this vulnerability is linked to a campaign aimed at inflating developer reputation scores for token rewards, making it a significant threat to developers and users relying on npm packages.

How To Fix

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

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

Conclusion

The weak_clam_z3n package poses a significant security risk due to its malicious code that alters package metadata and pollutes the npm registry. It is essential to take immediate action by uninstalling the package and monitoring for updates to ensure the security of your projects.

See every vulnerability recorded for weak_clam_z3n →

Share this vulnerability

FAQ

The weak_clam_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code modifies your package.json file, potentially leading to security vulnerabilities and the pollution of the npm registry.

You should uninstall the weak_clam_z3n package immediately and monitor for any updates or patches from the npm registry.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

Regularly update your dependencies, use tools like Vulert for monitoring, and review package sources before installation to mitigate risks.

How To Fix

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

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