Malicious Code Injection in complete_ferret-strongdev Package

complete_ferret-strongdev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100767: Malicious code in complete_ferret-strongdev (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 complete_ferret-strongdev package is part of the npm ecosystem, often utilized for various development tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is designed to manipulate its own metadata and create numerous derivative packages, which can lead to significant security risks for developers using it.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the complete_ferret-strongdev package. This payload modifies the package.json file by removing private flags and altering version numbers, which allows the package to republish itself under random names. The intent is to inflate developer reputation scores for token rewards, leading to a polluted npm registry and potential exploitation of developers who unknowingly use these compromised packages.

How To Fix

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

npm uninstall complete_ferret-strongdev

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 monitor your project dependencies using tools like Vulert. By utilizing the Vulert playground, you can check if your application is affected by this vulnerability without needing to sign up. Visit https://vulert.com/scanner to access the playground.

Conclusion

The complete_ferret-strongdev package poses a significant security risk due to its malicious code designed to manipulate package metadata and republish itself. It is crucial for developers to remove this package and utilize tools like Vulert to monitor their projects for vulnerabilities.

See every vulnerability recorded for complete_ferret-strongdev →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to manipulate package metadata and inflate developer reputation scores.

The malicious code can lead to the republishing of compromised packages, potentially exposing your project to further vulnerabilities and security risks.

You should uninstall the complete_ferret-strongdev package immediately and check your project for any other compromised dependencies.

While many packages are safe, it is essential to monitor your dependencies and use tools like Vulert to identify any vulnerabilities in your project.

Regularly audit your dependencies, keep your packages updated, and use monitoring tools like Vulert to stay informed about potential vulnerabilities.

How To Fix

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

npm uninstall complete_ferret-strongdev

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