sf-i-events@1.0.1163
Superflows Navigation Component
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe active entrypoint sends existing service credentials to a publisher-selected endpoint during ordinary calendar navigation. This is a concrete credential disclosure, so the package should be blocked.
Decision evidence
public snapshot- package.json selects sf-i-events.js as the package entrypoint.
- The entrypoint sends email and access-token cookie values as Basic authorization to a hardcoded Lambda endpoint in a calendar request.
- A click handler activates that request; the endpoint is fixed in package code rather than selected by the caller.
- util.js reads the values from document.cookie and sends the authorization header in a POST request.
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.1163.
See all versions of sf-i-events for other recorded verdicts.
- Avoid installing sf-i-events@1.0.1163. 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.