Malicious Code Exploit in straight_manatee_replicate_automation Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109167: Malicious code in straight_manatee_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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The straight_manatee_replicate_automation package is part of the npm ecosystem, primarily used for automating tasks related to package management. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package's functionality is compromised, making it a vector for malicious activities.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded in the straight_manatee_replicate_automation package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then republished to the npm registry. The ramifications include potential exposure of sensitive information, pollution of the npm registry, and damage to developer reputation scores due to the proliferation of these malicious packages.

How To Fix

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

npm uninstall straight_manatee_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 remove the straight_manatee_replicate_automation package from your project using the following command: npm uninstall straight_manatee_replicate_automation. This will prevent the malicious code from executing until a fix is available.

Conclusion

The straight_manatee_replicate_automation package has been identified as containing malicious code that compromises the integrity of npm projects. Immediate action is required to mitigate the risks associated with this vulnerability, including uninstalling the package and monitoring for updates.

See every vulnerability recorded for straight_manatee_replicate_automation →

Share this vulnerability

FAQ

It is an npm package used for automating tasks related to package management, but it has been compromised with malicious code.

The malicious code modifies your package.json file, potentially exposing sensitive information and polluting the npm registry with unwanted packages.

You should immediately uninstall the package and check for any updates or patches that may address the vulnerability.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

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