Malicious Code Injection in weird_weasel_replicate_automation Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110800: Malicious code in weird_weasel_replicate_automation (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 weird_weasel_replicate_automation package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to automate tasks related to the generation and publication of derivative packages. However, it has been identified as malicious due to its functionality that modifies package metadata and publishes numerous variants to manipulate developer reputation scores.

Vulnerability Detail

The vulnerability originates from the package's malicious code, which alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the continuous republishing of these variants, polluting the npm registry and potentially compromising the integrity of the ecosystem. The malicious payload can inflate developer reputation scores fraudulently, impacting the trustworthiness of npm packages.

How To Fix

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

npm uninstall weird_weasel_replicate_automation

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 prevent the installation of the weird_weasel_replicate_automation package by using the following command: npm uninstall weird_weasel_replicate_automation. Additionally, you may want to audit your project's dependencies to ensure no other malicious packages are present.

Conclusion

The weird_weasel_replicate_automation package has been identified as malicious due to its ability to manipulate package metadata and publish variants that pollute the npm registry. It is crucial for developers to take immediate action to update or remove this package to protect their projects from potential risks.

See every vulnerability recorded for weird_weasel_replicate_automation →

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 vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies, potentially affecting your application's functionality.

You should update the package to a patched version if available or uninstall it from your project to mitigate the risk.

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

You can refer to the vulnerability details on the GitHub repository for malicious packages or consult the npm registry for updates.

How To Fix

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

npm uninstall weird_weasel_replicate_automation

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