registry / @xapp/contact-app / 1.97.0
@xapp/contact-app@1.97.0
Booking & Contact Page for Form Widget
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInspected source behavior is consistent with a browser contact-form application, including configured authentication, form conditions, and conversion tracking. No concrete malicious behavior or installation attack chain was found.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Importing the library or rendering the standalone contact page activates browser functionality; building explicitly activates the Git query.
Impact
Expected contact-form and analytics activity; no confirmed malicious impact was established.
Mechanism
The package renders configured widgets and sends form data to configured services. No malicious installation, credential harvesting, or agent-control mutation was identified.
AI rationale
Inspected source behavior is consistent with a browser contact-form application, including configured authentication, form conditions, and conversion tracking. No concrete malicious behavior or installation attack chain was found.
Network endpoints4
form.xapp.ai/config.json?key=api.xapp.ai/graphqlconnect.facebook.net/en_US/fbevents.jsbzrcdn.openai.com/sdk/oaiq.min.js
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines development scripts without install lifecycle hooks or a runtime self-dependency.
- rollup.config.js runs a fixed Git branch query during an explicit build.
- The standalone bundle fetches contact-page configuration from form.xapp.ai.
- The ES bundle sends form requests using the configured endpoint and caller-provided widget key.
- The CommonJS entrypoint renders the configured contact form.
- Dynamic functions implement configured form conditions; tracking code handles marketing identifiers and configured conversion pixels.
Evidence against
Behavioral surface
ChildProcessEnvironmentVarsEvalNetworkShell
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
7 flaggedrollup.config.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @xapp/contact-app@1.101.2
matchedIdentity = npm:QHhhcHAvY29udGFjdC1hcHA:1.101.2
similarity = 0.519
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
rollup.config.jsView on unpkg22import replace from "rollup-plugin-replace";
L23: import { execSync } from "child_process";
L24:
High
dist/xapp-contact-page.jsView file
193contains invisible/control Unicode U+2066 (left-to-right isolate)
function(e){var t=Ob.default,n=vb.default;Object.defineProperty(e,"__esModule",{value:!0});var r={chainPropTypes:!0,deepmerge:!0,isPlainObject:!0,elementAcceptingRef:!0,elementTypeAcceptingRef:!0,exactProp:!0,formatMuiErrorMessage:!0,getDis
Findings
4 Critical3 High3 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationdist/index.es.js
CriticalTrojan Source Unicodedist/xapp-contact-page.js
CriticalTrigger Reachable Dangerous Capabilitydist/index.js
CriticalPrevious Version Dangerous Deltarollup.config.js
HighChild Processrollup.config.js
HighShell
HighSame File Env Network Executiondist/xapp-contact-page.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowEvaldist/xapp-contact-page.js
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @xapp/contact-app@1.97.0.
See all versions of @xapp/contact-app for other recorded verdicts.
- Review the evidence and your use of @xapp/contact-app@1.97.0 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.