Malicious Code Injection in capable_goose-silentdev Package

capable_goose-silentdev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100257: Malicious code in capable_goose-silentdev (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 capable_goose-silentdev package is part of the npm ecosystem, typically utilized for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate developer reputation scores through automated scripts that publish numerous variants of itself.

Vulnerability Detail

The vulnerability stems from the package's involvement in a token reward campaign that utilizes autopublish scripts to generate and publish derivative packages with randomized names. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, leading to pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly use this package, as it can compromise their projects and inflate the npm registry with unwanted packages.

How To Fix

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

npm uninstall capable_goose-silentdev

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 capable_goose-silentdev package from your project by executing the following command: npm uninstall capable_goose-silentdev. This will prevent any malicious code from executing until a safe version is available.

Conclusion

The capable_goose-silentdev package poses a significant risk due to its malicious code injection, which can compromise projects and pollute the npm registry. It is crucial to take immediate action by updating or removing the package and monitoring your project for vulnerabilities using tools like Vulert.

See every vulnerability recorded for capable_goose-silentdev →

Share this vulnerability

FAQ

capable_goose-silentdev is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

The vulnerability can lead to the introduction of malicious code into your project, compromising its security and potentially affecting its functionality.

If you have installed capable_goose-silentdev, it is recommended to uninstall it immediately and check for any updates or patches for your other dependencies.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. By analyzing your package-lock.json, it provides insights into potential risks.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall capable_goose-silentdev

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