Vulnerability Database · npm · hyper-fullfacing · Version
hyper-fullfacing 1.0.1
1.0.1 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 1.0.2.
Critical 1 High 0 Medium 0 Low 0 Unrated 0
-
Released 26 Feb 2017
Licence MIT
Also known from other sources 0
Newer releases 3
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
hyper-fullfacing 1.0.1 vulnerabilities
1 vulnerability cover hyper-fullfacing 1.0.1. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Critical Security Breach in hyper-fullfacing: Malicious Code Exploitation | N/A critical | No fix published | 25 Nov 2025 |
Looking for another version, or everything Vulert holds for hyper-fullfacing?
Questions
About hyper-fullfacing 1.0.1
Is hyper-fullfacing 1.0.1 vulnerable?
Yes. 1 vulnerability in the Vulert database cover hyper-fullfacing 1.0.1: 1 critical, 0 high, 0 medium and 0 low. The upgrade Vulert recommends is 1.0.2, and each entry above names the fixed version to move to.
Which version of hyper-fullfacing should I use instead of 1.0.1?
1.0.2 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 1.0.1 the latest release of hyper-fullfacing?
No. 1.0.1 was published 26 Feb 2017, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
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 hyper-fullfacing for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the hyper-fullfacing version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.