Vulnerability Database · npm · client-controls-module · Version

client-controls-module 0.0.1-security

0.0.1-security 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 23 May 2025 Status latest release 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

client-controls-module 0.0.1-security vulnerabilities

1 vulnerability cover client-controls-module 0.0.1-security. Open the full list in the database.

Vulnerability Severity Fixed version Disclosed
Critical Malicious Code Vulnerability in client-controls-module N/A critical No fix published 23 May 2025

Looking for another version, or everything Vulert holds for client-controls-module?

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 client-controls-module 0.0.1-security

Is client-controls-module 0.0.1-security vulnerable?

Yes. 1 vulnerability in the Vulert database cover client-controls-module 0.0.1-security: 1 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.

Is 0.0.1-security the latest release of client-controls-module?

Yes. 0.0.1-security is the current release, published 23 May 2025. 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 client-controls-module for upcoming vulnerabilities?

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