@xapp/contact-app@1.101.15
Booking & Contact Page for Form Widget
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe bundle automatically sends incomplete form contents on page exit, without an explicit submission. The destination is the widget’s configured service and the package is a contact form, so the behavior is suspicious telemetry rather than clear malicious exfiltration.
Decision evidence
public snapshot- A beforeunload handler sends accumulated partial form data with abandonmentReason "close_tab" when the user leaves before completing the form.
- The partial-data event includes tracking metadata such as user agent, timezone, language, screen and viewport dimensions, and page URL.
- The event beacon sends a POST to the configured service origin at /cms/widget/events, including the widget key and event data.
- The package describes itself as a stand-alone contact and scheduling page, so sending completed form submissions to its service fits its purpose.
- The README documents automatic capture and persistence of marketing tracking parameters for form API requests.
- The manifest has no install or lifecycle scripts; its entry points are browser bundles.
Source & flagged code
5 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/xapp-contact-page.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @xapp/contact-app@1.101.15.
See all versions of @xapp/contact-app for other recorded verdicts.
- Review the evidence and your use of @xapp/contact-app@1.101.15 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.