Vulnerability Database · npm · hardhat-node · Version
hardhat-node 99.0.0-dummy
99.0.0-dummy 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: 99.0.0-dummy.
Critical 1 High 0 Medium 0 Low 0 Unrated 0
-
Released 28 Feb 2026
Status latest release
Also known from other sources 0
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
hardhat-node 99.0.0-dummy vulnerabilities
1 vulnerability cover hardhat-node 99.0.0-dummy. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Malicious Code Detected in hardhat-node Package - Version 1.0.2 | N/A critical | No fix published | 26 Feb 2026 |
Looking for another version, or everything Vulert holds for hardhat-node?
Questions
About hardhat-node 99.0.0-dummy
Is hardhat-node 99.0.0-dummy vulnerable?
Yes. 1 vulnerability in the Vulert database cover hardhat-node 99.0.0-dummy: 1 critical, 0 high, 0 medium and 0 low. The upgrade Vulert recommends is 99.0.0-dummy, and each entry above names the fixed version to move to.
Which version of hardhat-node should I use instead of 99.0.0-dummy?
99.0.0-dummy is the version Vulert recommends for this release line, which is also the release the publisher currently ships. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 99.0.0-dummy the latest release of hardhat-node?
Yes. 99.0.0-dummy is the current release, published 28 Feb 2026. 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 hardhat-node for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the hardhat-node version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.