supply chain event / NVI-00010965 / Revision 1
Malicious code in hardhat-roof (npm)
GitHub lists this malware advisory for hardhat-roof. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
hardhat-roof
source listed= 2.21.0
## Source: amazon-inspector (25cbf03ad6014824ab078237f83b2b682145928e5effefbe3dcc5deca9ba1e26) The package presents itself as the pino logger — README, docs/, index.d.ts and LICENSE are copied from pinojs/pino and keywords advertise 'fast, logger, stream, json' — but the package name is 'hardhat-roof', the description references unrelated vulnerability-management functionality, and the author points to jsonspack.com rather than the pino maintainers. The top of index.js executes `require('./lib/config')`, which loads lib/config.js: a 4,373,384-byte file containing obfuscator.io-style string-array obfuscation with a self-rotating decoder (`n'push')` loop gated by a parseInt sum), hex-escaped character lookups, and dozens of single-letter indirection functions. The remaining lib/ files are small and consistent with pino; only config.js is the oversized opaque blob, and the real pino has no such file. Any consumer that imports or requires this package therefore executes several megabytes of opaque code in-process at load time. The combination of a doppelganger cover story cloned from a popular logger, a mismatched package name and author, and a reachable load-time execut
03 / Response
What to do next
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-99j2-pxrq-hpqc ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.