sf-i-events@1.0.1165
Superflows Navigation Component
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe active calendar request discloses existing service credentials to a hard-coded recipient unrelated to the package's configurable API endpoint. This is concrete credential exfiltration behavior, so the package should be blocked.
Static reason
One or more suspicious static signals were detected.
Trigger
The user clicks the calendar mapping button.
Impact
The endpoint receives the user's service credentials; successful receipt or subsequent use is not established by source inspection.
Mechanism
The component reads email and accessToken cookies, encodes them as Basic authorization, and sends them in a POST request to the fixed endpoint.
Attack narrative
Clicking the calendar mapping button invokes a request to a fixed AWS Lambda URL. The component reads the email and accessToken cookies and passes their encoded value to the shared request helper, which sends it as Basic authorization in a POST. The inspected path has no recipient-specific consent check. The source does not establish whether the endpoint successfully receives or uses the credentials.
AI rationale
The active calendar request discloses existing service credentials to a hard-coded recipient unrelated to the package's configurable API endpoint. This is concrete credential exfiltration behavior, so the package should be blocked.
Evidence
sf-i-events.jsutil.js
Network endpoints1
3mefupehxkw4pwsq3oyk7lf2pq0pisdx.lambda-url.us-east-1.on.aws/schedulegetcalendarjob
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The calendar request uses a hard-coded AWS Lambda URL and builds authorization from the email and accessToken cookies.
- The request helper sends the authorization in a Basic header with an HTTP POST; the utility reads values from document.cookie.
- A calendar mapping button invokes this request path, with no recipient-specific consent check in the inspected path.
Evidence against
Behavioral surface
EnvironmentVarsNetwork
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
Source & flagged code
6 flagged · loading sourcedev/templates/table-template.docxView file
•path = dev/templates/table-template.docx
kind = high_entropy_blob
sizeBytes = 5507
magicHex = [redacted]
High
Ships High Entropy Blob
Package ships high-entropy non-source blobs.
dev/templates/table-template.docxView on unpkg•path = dev/templates/table-template.docx
kind = compressed_blob
sizeBytes = 5507
magicHex = [redacted]
Medium
Ships Compressed Blob
Package ships compressed or archive-like blobs.
dev/templates/table-template.docxView on unpkg•path = dev/templates/table-template.docx
kind = nested_archive_needs_inspection
sizeBytes = 5507
magicHex = [redacted]
Low
Nested Archive Needs Inspection
Package ships a nested archive or MCP bundle that was inventoried but not recursively analyzed.
dev/templates/table-template.docxView on unpkgFindings
2 High6 Medium4 Low
HighShips High Entropy Blobdev/templates/table-template.docx
HighNode Builtin Dependency Squatpackage.json
MediumNetwork
MediumEnvironment Vars
MediumShips Compressed Blobdev/templates/table-template.docx
MediumStructural Risk Force Deep Review
MediumStripped Provenance Metadatasf-i-events.js
MediumStripped Provenance Metadatasf-i-events.js
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
LowNested Archive Needs Inspectiondev/templates/table-template.docx
Affected versions and remediation
This report applies to sf-i-events@1.0.1165.
See all versions of sf-i-events for other recorded verdicts.
- Avoid installing sf-i-events@1.0.1165. 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.