Malicious Code Injection in brainy_wallaby_replicate_automation Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100079: Malicious code in brainy_wallaby_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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The brainy_wallaby_replicate_automation package is part of the npm ecosystem, designed to facilitate automation tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is particularly vulnerable due to its involvement in generating and publishing random packages that can compromise developer reputation and pollute the registry.

Vulnerability Detail

The vulnerability originates from the package's association with the tea.xyz token reward campaign, which employs scripts to automatically create and publish derivative packages with randomized names. The malicious payload alters the package.json file by removing private flags, changing version numbers, and continuously republishing variants, leading to potential security risks and a polluted npm registry.

How To Fix

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

npm uninstall brainy_wallaby_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 workaround, you can avoid using the brainy_wallaby_replicate_automation package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The brainy_wallaby_replicate_automation package has been identified as containing malicious code that can compromise the integrity of your project. It is crucial to uninstall this package and seek alternatives to ensure the security of your application.

See every vulnerability recorded for brainy_wallaby_replicate_automation →

Share this vulnerability

FAQ

It is an npm package designed for automation tasks but has been compromised by malicious code.

It can lead to the pollution of the npm registry and compromise your project's security by introducing malicious code.

You should uninstall the package immediately using 'npm uninstall brainy_wallaby_replicate_automation'.

Currently, there is no patched version available for the brainy_wallaby_replicate_automation package.

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

How To Fix

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

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