@hashbrownai/openai@0.8.1
OpenAI provider for Hashbrown AI
AI Security Review
scanned 11d ago · by lpm-firewall-aiSource inspection confirms automatic install-time collection of identifying metadata without an affirmative consent gate. The publisher-owned endpoint and absence of a separate attack keep this at warning severity.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Installing the package while telemetry opt-out variables are unset.
Impact
The publisher receives identifying installation and potentially Git identity data during package installation.
Mechanism
The hook gathers a persistent installation identifier and environment details, optionally adds Git identity, and posts the event to the default collection endpoint.
AI rationale
Source inspection confirms automatic install-time collection of identifying metadata without an affirmative consent gate. The publisher-owned endpoint and absence of a separate attack keep this at warning severity.
Evidence
package.jsoninstall/postinstall.cjsinstall/collector.cjsinstall/policy.cjsinstall/identity.cjsinstall/git-context.cjs~/.hashbrown/installation-id
Network endpoints1
hashbrown.dev/_/growth/collect/v1/install
Decision evidence
public snapshotAI called this Suspicious at 84.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package runs a postinstall hook that starts the installation collector automatically.
- The collector sends an installation event with package, environment, and persistent installation identifier data to the default Hashbrown endpoint.
- The event can include Git display name and email; collection is disabled only when opt-out variables are set.
- The endpoint defaults to Hashbrown’s collection service, and external overrides are rejected in favor of that default.
Evidence against
- The recipient is on the package publisher’s domain, and the source shows no unrelated recipient or credential collection.
- The package’s runtime entry point exposes an OpenAI adapter; the installation report is separate from that adapter behavior.
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 unpkg36"scripts": {
"postinstall": "node install/postinstall.cjs"
}
}
Medium
Suspicious Lifecycle Evidence
The package runs a postinstall hook that starts the installation collector automatically.
package.jsonView on unpkg · L36install/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/openai@0.8.1.
See all versions of @hashbrownai/openai for other recorded verdicts.
- Review the evidence and your use of @hashbrownai/openai@0.8.1 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.