css-hgwctv-polyfill
CSS polyfill utility
This report shows the evidence for css-hgwctv-polyfill@1.0.0, the only known version.
AI Security Review
scanned 18d ago · by lpm-firewall-aiInspected source proves automatic system reconnaissance and external data transmission unrelated to a CSS polyfill. This is an active data-exfiltration attack when the registry module is loaded, despite the inert default entrypoint.
Decision evidence
public snapshot- thunderboltRegistry.js sends collected data and the hostname to a fixed external HTTP callback.
- Loading thunderboltRegistry.js immediately executes system commands and forwards their output.
- The module reads /etc/hosts and sends its contents to the callback.
- registry-manifest.min.json maps registry assets to the executable module.
- package.json explicitly includes the registry manifest and executable module in published files.
- There are no install lifecycle hooks, and index.js only exports an empty object.
- The attack requires loading the registry module; importing the default entrypoint does not activate it.
Source & flagged code
8 flagged · loading sourceSource gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
thunderboltRegistry.jsView on unpkg · L10Source file is highly similar to a previously finalized malicious package; route for source-aware review.
thunderboltRegistry.jsView on unpkgFindings
Affected versions and remediation
This report applies to css-hgwctv-polyfill@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing css-hgwctv-polyfill@1.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.