@hashbrownai/openai@0.8.0
OpenAI provider for Hashbrown AI
AI Security Review
scanned 13d ago · by lpm-firewall-aiSource inspection confirms automatic, publisher-directed installation telemetry that can disclose persistent and personal identifying data. The first-party endpoint and opt-out controls reduce concern, but do not resolve the lack of affirmative consent for Git identity collection.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
Installing the package with postinstall scripts enabled, unless a telemetry opt-out flag is set.
Impact
The publisher receives a persistent installation identifier and may receive the developer's configured Git name, email, and repository metadata.
Mechanism
The hook gathers installation and environment details, reads Git identity, then posts an event to the fixed Hashbrown collector. Git identity is omitted in CI; endpoint overrides are limited to loopback.
AI rationale
Source inspection confirms automatic, publisher-directed installation telemetry that can disclose persistent and personal identifying data. The first-party endpoint and opt-out controls reduce concern, but do not resolve the lack of affirmative consent for Git identity collection.
Evidence
package.jsoninstall/postinstall.cjsinstall/collector.cjsinstall/policy.cjsinstall/git-context.cjsinstall/identity.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 package runs its collector automatically from a postinstall hook.
- The collector sends a package installation event to the fixed Hashbrown endpoint; non-loopback endpoint overrides are rejected.
- Outside CI, the event can include Git identity read from global or checkout configuration, including a configured name and email.
- The hook creates or reuses a persistent installation identifier in the user's .hashbrown directory and includes it in the event.
- Telemetry can be disabled through documented environment flags, but collection has no affirmative opt-in gate.
- The inspected runtime hint subscribes to UI runtime state and reads its status; it does not show an account action.
Evidence against
- The collector is aligned with the Hashbrown package and sends to hashbrown.dev; its endpoint override is restricted to loopback.
- Git identity is omitted in CI, and the install hook honors telemetry opt-out flags.
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 unpkg37"postinstall": "node install/postinstall.cjs"
}
}
Medium
Suspicious Lifecycle Evidence
The package runs its collector automatically from a postinstall hook.
package.jsonView on unpkg · L37install/git-context.cjsView file
Findings
3 High6 Medium3 Low
HighInstall Time Lifecycle Scriptspackage.json
HighKnown Malware Source Similarityinstall/git-context.cjs
HighPrevious Version Dangerous Deltainstall/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
LowScripts Present
LowFilesystem
LowUrl Strings
Affected versions and remediation
This report applies to @hashbrownai/openai@0.8.0.
See all versions of @hashbrownai/openai for other recorded verdicts.
- Review the evidence and your use of @hashbrownai/openai@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.