sf-i-events@1.0.1133
Superflows Navigation Component
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe active credential-forwarding path reaches a caller-configured destination without a visible allowlist. This is a dangerous capability rather than confirmed malware because no package-controlled recipient or covert trigger was established.
Decision evidence
public snapshot- The browser component builds a request URL from its apiId property, so the credential destination is caller-configured.
- The component reads email and accessToken cookies, encodes them, and passes the result to its request helper.
- The helper sends that value as a Basic Authorization header to the supplied URL.
- The manifest declares a browser module entrypoint and contains no install lifecycle hook.
- The inspected request path is part of an event-details operation and does not show a hidden package-owned recipient.
- No install-time execution, shell execution, or remote payload loader was identified in the inspected entrypoint and helper.
Source & flagged code
6 flagged · loading sourcePackage ships high-entropy non-source blobs.
dev/templates/table-template.docxView on unpkgPackage ships compressed or archive-like blobs.
dev/templates/table-template.docxView on unpkgPackage ships a nested archive or MCP bundle that was inventoried but not recursively analyzed.
dev/templates/table-template.docxView on unpkgFindings
Affected versions and remediation
This report applies to sf-i-events@1.0.1133.
See all versions of sf-i-events for other recorded verdicts.
- Review the evidence and your use of sf-i-events@1.0.1133 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.