Vulnerability Database · npm · complete_ferret-strongdev · Version

complete_ferret-strongdev 3.3.1

3.3.1 is affected by 1 vulnerability.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to.

Critical 1 High 0 Medium 0 Low 0 Unrated 0

Released 18 May 2024 Status latest release Licence ISC Also known from other sources 1 Newer releases 1 Database updated 23/Oct/2026

Release and licence data published by the npm registry. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Vulnerabilities affecting this version

complete_ferret-strongdev 3.3.1 vulnerabilities

1 vulnerability cover complete_ferret-strongdev 3.3.1. Open the full list in the database.

Vulnerability Severity Fixed version Disclosed
Malicious Code Injection in complete_ferret-strongdev Package N/A critical No fix published 11 Nov 2025

Looking for another version, or everything Vulert holds for complete_ferret-strongdev?

All versions → Full vulnerability list →

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 →

Questions

About complete_ferret-strongdev 3.3.1

Is complete_ferret-strongdev 3.3.1 vulnerable?

Yes. 1 vulnerability in the Vulert database cover complete_ferret-strongdev 3.3.1: 1 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.

Is 3.3.1 the latest release of complete_ferret-strongdev?

Yes. 3.3.1 is the current release, published 18 May 2024. Staying on the current line is what keeps you inside the publisher's fixes.

What does a malicious-package vulnerability mean?

It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.

How do I monitor complete_ferret-strongdev for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the complete_ferret-strongdev version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.