@hashbrownai/angular@0.8.3
Angular bindings for Hashbrown AI
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe install hook performs package-aligned telemetry, but sends a persistent identifier and potentially personal Git identity without an affirmative opt-in. The endpoint and scope support a warning for privacy exposure, not a publish block.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Installing the package when telemetry opt-out variables are unset.
Impact
The collector may receive a persistent installation identifier and the user's configured Git display name and email.
Mechanism
The postinstall hook collects installation details and sends them to the default Hashbrown endpoint; an endpoint override is accepted only for loopback hosts.
AI rationale
The install hook performs package-aligned telemetry, but sends a persistent identifier and potentially personal Git identity without an affirmative opt-in. The endpoint and scope support a warning for privacy exposure, not a publish block.
Evidence
package.jsoninstall/postinstall.cjsinstall/collector.cjsinstall/policy.cjsinstall/git-context.cjsinstall/identity.cjs
Network endpoints1
hashbrown.dev/_/growth/collect/v1/install
Decision evidence
public snapshotAI called this Suspicious at 89.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package runs an automatic postinstall hook that starts install-event collection.
- The event can include package and system details plus available Git identity outside CI, and the collector sends it as a batch.
- Git identity collection includes the configured display name and email.
- The collector creates or reuses a persistent installation identifier in the user’s home directory.
- The default recipient is the Hashbrown installation collector; endpoint overrides are accepted only for loopback hosts.
- Telemetry opt-out variables are supported, but collection otherwise proceeds without an affirmative opt-in.
Evidence against
- The collector is package-aligned telemetry sent to the Hashbrown endpoint, and the source shows no unrelated recipient or broader attack behavior.
- CI installations omit Git identity, and several opt-out variables disable collection.
Behavioral surface
CryptoEnvironmentVarsFilesystemNetwork
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 unpkg46dule",
"scripts": {
"postinstall": "node install/postinstall.cjs"
}
}
Medium
Suspicious Lifecycle Evidence
The package runs an automatic postinstall hook that starts install-event collection.
package.jsonView on unpkg · L46install/git-context.cjsView file
Findings
3 High6 Medium3 Low
HighInstall Time Lifecycle Scriptspackage.json
HighKnown Malware Source Similarityinstall/git-context.cjs
HighKnown Malware Source Similarityinstall/policy.cjs
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumSuspicious Lifecycle Evidencepackage.json
MediumSuspicious Lifecycle Evidenceinstall/postinstall.cjs
MediumAi Review Evidenceinstall/collector.cjs
LowScripts Present
LowFilesystem
LowUrl Strings
Affected versions and remediation
This report applies to @hashbrownai/angular@0.8.3.
See all versions of @hashbrownai/angular for other recorded verdicts.
- Review the evidence and your use of @hashbrownai/angular@0.8.3 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.