Malicious Code Injection in partial_marmoset_replicate_automation Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106918: Malicious code in partial_marmoset_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 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 partial_marmoset_replicate_automation package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package, like many others, is intended to facilitate automation tasks. However, it has been compromised as part of a malicious campaign that aims to manipulate the npm registry by generating and publishing numerous derivative packages with altered metadata.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the partial_marmoset_replicate_automation package. This payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names. The intent is to inflate developer reputation scores through the tea.xyz token reward campaign, leading to pollution of the npm registry with these derivative packages. This can result in security risks for developers who unknowingly use these compromised packages, as they may introduce vulnerabilities into their applications.

How To Fix

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

npm uninstall partial_marmoset_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 avoid using the partial_marmoset_replicate_automation package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The partial_marmoset_replicate_automation package has been identified as containing malicious code that can compromise the integrity of applications using it. It is crucial to uninstall this package and monitor your projects for vulnerabilities to ensure security.

See every vulnerability recorded for partial_marmoset_replicate_automation →

Share this vulnerability

FAQ

It is an npm package intended for automation tasks but has been compromised to include malicious code.

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

You should uninstall the package immediately using the command npm uninstall partial_marmoset_replicate_automation.

Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

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