@heycatch/sdk
HeyCatch SDK
This report shows the evidence for @heycatch/sdk@0.8.5. 1 of 7 known versions is blocked or flagged. See all versions.
AI Security Review
scanned 2h ago · by lpm-firewall-aiThe browser-session hijack hint was not substantiated: identity changes require an SDK API call. However, the bundled diagnostic explicitly directs readers to external agent instructions, which is a review boundary escape and evidence of malicious intent under the review rules.
Decision evidence
public snapshot- A bundled diagnostic directs readers to “re-verify against https://heycatch.ai/agents.md,” sending the review outside the package boundary.
- That text is part of an internal development-build refusal diagnostic; the package sets its stage to prod, making that diagnostic unreachable in this build.
- The browser and server entry points are selected through package exports, with no lifecycle scripts in the manifest.
- Identity changes are exposed through an SDK API and require a call; I found no code that reuses an authenticated browser session to mutate account settings.
Source & flagged code
4 flaggedBrowser source reuses an authenticated session to collect identity data and mutate account settings while reporting externally.
dist/index.jsView on unpkg · L1A bundled diagnostic directs readers to “re-verify against https://heycatch.ai/agents.md,” sending the review outside the package boundary.
dist/index.jsView on unpkg · L1That text is part of an internal development-build refusal diagnostic; the package sets its stage to prod, making that diagnostic unreachable in this build.
dist/index.jsView on unpkg · L1That text is part of an internal development-build refusal diagnostic; the package sets its stage to prod, making that diagnostic unreachable in this build.
dist/index.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @heycatch/sdk@0.8.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing @heycatch/sdk@0.8.5. 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.