Malicious Code Injection in worthwhile_ptarmigan_replicate_automation Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-111027: Malicious code in worthwhile_ptarmigan_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 worthwhile_ptarmigan_replicate_automation package is part of the npm ecosystem, primarily used for automation tasks. It is designed to facilitate various automation processes but has been compromised. This package is linked to a token reward campaign that exploits npm's publishing system, leading to potential security risks for developers and users who rely on it.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the worthwhile_ptarmigan_replicate_automation package. This code 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. This behavior not only pollutes the registry but also compromises the integrity of the developer's reputation and can lead to unintended consequences for applications relying on this package.

How To Fix

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

npm uninstall worthwhile_ptarmigan_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 worthwhile_ptarmigan_replicate_automation package altogether. If it is already in use, consider replacing it with an alternative package that provides similar functionality without the associated risks.

Conclusion

The worthwhile_ptarmigan_replicate_automation package has been compromised with malicious code that alters its functionality and can lead to significant security risks. It is crucial to update or remove this package to protect your applications. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for worthwhile_ptarmigan_replicate_automation →

Share this vulnerability

FAQ

The malicious code originates from a token reward campaign that exploits npm's publishing system, flooding it with compromised packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

Using this package can lead to security vulnerabilities, including the potential exposure of sensitive information and the pollution of the npm registry.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.

If you cannot update the package, consider removing it from your project and replacing it with a safer alternative until a secure version is available.

How To Fix

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

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