@hashbrownai/react@0.8.0
React components for Hashbrown AI
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe active postinstall automatically transmits persistent installation and, outside CI, configured Git identity data to a package-aligned endpoint unless an opt-out is set. This warrants a warning about default identity disclosure, but source inspection did not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Installing the package when its postinstall lifecycle runs and telemetry has not been disabled.
Impact
The vendor can associate installation events with a persistent ID and, outside CI, the configured Git display name and email.
Mechanism
The collector reads installation and Git identity data, builds a package-installed event, and posts it to the Hashbrown endpoint.
AI rationale
The active postinstall automatically transmits persistent installation and, outside CI, configured Git identity data to a package-aligned endpoint unless an opt-out is set. This warrants a warning about default identity disclosure, but source inspection did not establish malicious behavior.
Evidence
package.jsoninstall/postinstall.cjsinstall/collector.cjsinstall/identity.cjsinstall/git-context.cjsinstall/policy.cjs~/.hashbrown/installation-id
Network endpoints1
hashbrown.dev/_/growth/collect/v1/install
Decision evidence
public snapshotAI called this Suspicious at 82.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest runs a postinstall collector, and the hook checks that it is running as the package manager’s postinstall process.
- The collector builds an install event with package and machine metadata and sends it as an HTTP POST; it also includes a per-user installation ID.
- Outside CI, the event can include Git display name and email from configured Git identity.
- Collection has opt-out variables and sends by default to the Hashbrown install endpoint, with endpoint overrides restricted to loopback addresses.
Evidence against
- The install event is package-aligned telemetry, and source provides opt-outs; the inspected code does not establish a hostile recipient or malicious payload behavior.
- The runtime entrypoints expose React components and hooks; the inspected dependencies implement JSON and Markdown parsing.
Behavioral surface
CryptoEnvironmentVarsFilesystemNetwork
UrlStrings
Source & flagged code
7 flaggedpackage.jsonView file
•scripts.postinstall = node install/postinstall.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node install/postinstall.cjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkg63"postinstall": "node install/postinstall.cjs"
}
}
Medium
Suspicious Lifecycle Evidence
The manifest runs a postinstall collector, and the hook checks that it is running as the package manager’s postinstall process.
package.jsonView on unpkg · L63install/git-context.cjsView file
Findings
2 High7 Medium3 Low
HighInstall Time Lifecycle Scriptspackage.json
HighKnown Malware Source Similarityinstall/git-context.cjs
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumSuspicious Lifecycle Evidencepackage.json
MediumSuspicious Lifecycle Evidenceinstall/postinstall.cjs
MediumAi Review Evidenceinstall/collector.cjs
MediumAi Review Evidenceinstall/identity.cjs
LowScripts Present
LowFilesystem
LowUrl Strings
Affected versions and remediation
This report applies to @hashbrownai/react@0.8.0.
See all versions of @hashbrownai/react for other recorded verdicts.
- Review the evidence and your use of @hashbrownai/react@0.8.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.