@cleartrip/ct-platform-hotel-cross-sell-lpg-content@4.8.0
Hotel cross sell LPG content Component
AI Security Review
scanned 5d ago · by lpm-firewall-aiThis is a hotel cross-sell UI component, and its analytics events align with displaying and interacting with that UI. However, the events include trip and loyalty details, and the inspected package provides no disclosure or opt-out, so this is suspicious runtime telemetry rather than a confirmed attack.
Decision evidence
public snapshot- The component emits runtime analytics containing a trip ID, destination, travel dates, and loyalty type.
- A screen event fires when the component is not loading and its know-more state is active; an impression event also carries trip details.
- The bundle exposes a UI action event when the user clicks “View more details.”
- The events appear tied to the component’s screen, impression, and user-action behavior.
- The inspected bundle contains no hard-coded network endpoint; the analytics transport is delegated to ct-platform-utils.
- The package metadata identifies this as a hotel cross-sell content component and declares no install lifecycle scripts.
Source & flagged code
5 flaggedThe component emits runtime analytics containing a trip ID, destination, travel dates, and loyalty type.
dist/ct-platform-hotel-cross-sell-lpg-content.esm.jsView on unpkg · L1A screen event fires when the component is not loading and its know-more state is active; an impression event also carries trip details.
dist/ct-platform-hotel-cross-sell-lpg-content.esm.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @cleartrip/ct-platform-hotel-cross-sell-lpg-content@4.8.0.
See all versions of @cleartrip/ct-platform-hotel-cross-sell-lpg-content for other recorded verdicts.
- Review the evidence and your use of @cleartrip/ct-platform-hotel-cross-sell-lpg-content@4.8.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.