@hashbrownai/angular@0.8.2
Angular bindings for Hashbrown AI
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package’s default postinstall sends Git identity, including the configured name and email, along with install context to its vendor endpoint without an explicit consent prompt. This is install-time collection of user and project data, so the package should be blocked.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Package installation runs the postinstall hook unless the user disables scripts or sets a telemetry opt-out.
Impact
Git identity and project-related metadata can be disclosed during installation without an explicit collection prompt.
Mechanism
The collector reads Git name and email and checkout context, adds identity and install environment fields to an event, then POSTs the batch to hashbrown.dev.
Attack narrative
Installation triggers a postinstall collector that reads Git identity and checkout context, includes identity and environment details in an install event, and sends the batch to hashbrown.dev. Opt-outs and CI handling do not provide consent for the default collection of Git name and email during installation.
AI rationale
The package’s default postinstall sends Git identity, including the configured name and email, along with install context to its vendor endpoint without an explicit consent prompt. This is install-time collection of user and project data, so the package should be blocked.
Evidence
package.jsoninstall/postinstall.cjsinstall/collector.cjsinstall/git-context.cjsinstall/policy.cjs~/.gitconfig$XDG_CONFIG_HOME/git/config<consumer checkout>/.git/config<consumer checkout>/.git/config.worktree
Network endpoints1
hashbrown.dev/_/growth/collect/v1/install
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package runs install/postinstall.cjs automatically during postinstall.
- The install collector reads Git identity and checkout context, including Git display name and email.
- The install event can include collected identity and environment details, then sends the batch in an HTTP POST.
- The default telemetry endpoint is https://hashbrown.dev/_/growth/collect/v1/install.
Evidence against
- Collection has opt-out checks and skips attaching Git identity in CI.
- The collector limits its run time and treats collection or transport failures as non-fatal.
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 unpkg46"type": "module",
"scripts": {
"postinstall": "node install/postinstall.cjs"
}
}
High
Suspicious Lifecycle Evidence
The package runs install/postinstall.cjs automatically during postinstall.
package.jsonView on unpkg · L46•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 unpkginstall/git-context.cjsView file
Findings
6 High3 Medium3 Low
HighInstall Time Lifecycle Scriptspackage.json
HighKnown Malware Source Similarityinstall/git-context.cjs
HighKnown Malware Source Similarityinstall/policy.cjs
HighSuspicious Lifecycle Evidenceinstall/postinstall.cjs
HighSuspicious Lifecycle Evidencepackage.json
HighAi Review Evidenceinstall/git-context.cjs
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowUrl Strings
Affected versions and remediation
This report applies to @hashbrownai/angular@0.8.2.
See all versions of @hashbrownai/angular for other recorded verdicts.
- Avoid installing @hashbrownai/angular@0.8.2. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.