Is Legrooms+ for Google Flights safe?
legrooms+-for-google-flig is high risk. Legrooms+ bundles Vio.com's Hermes tracker, active on 37 hotel-site patterns regardless of extension use. It sent the hotel page's domain, type, and listing name to a Vio endpoint with an affiliate ID; a coded price endpoint didn't fire.…
Who publishes itNo other listings under this identity, 16 shared hostnames
No other listings under this identity, 16 shared hostnames
Shared hosts - 16 hostnames
Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.
legrooms+-for-google-flig findings
Hotel Search Pages You Visit Are Reported to Vio's Ad Network
Legrooms+ bundles Vio.com's Hermes tracker, active on 37 hotel-site patterns regardless of extension use.
It sent the hotel page's domain, type, and listing name to a Vio endpoint with an affiliate ID; a coded price endpoint didn't fire.
What actually happens
You browse to a supported hotel or travel site, such as Booking.com, in any open tab.
Legrooms+ doesn't need to be actively used for its flight-seat feature; the tracking module runs in the background on a matched page.
The bundled Vio Hermes tracking module reports the page you're viewing to a Vio.com analytics endpoint.
It sends the site name, the page type, and the name of the specific hotel listing you opened, tagged with the Legrooms+ affiliate ID.
Captured request
200 OK, observed during dynamic analysis while browsing Booking.com search-results and a hotel-listing page; four such requests fired across the two pages.
- accept
- */*
- x-api-key
- <redacted>
- content-type
- application/json
{ "properties": { "category": "System", "entity": "TargetedPage", "action": "Displayed", "analyticsContext": { "pageContext": { "pageDomain": "booking", "pageType": "searchResults" } }, "bookingContext": { "firstHotelName": "Beautiful 3 bedroom apartments in Shoreditch" }, "payload": { "anonymousId": "b3f2a9de-7c41-4e88-9a2f-114fbb2ad013", "affiliateName": "legrooms", "sdkVersion": "1.3.2" }, "anonymousId": "b3f2a9de-7c41-4e88-9a2f-114fbb2ad013", "name": "System_TargetedPage_Displayed" }}What Hermes reports about the page you're on
- Site you're browsingbooking
Identifies which travel or hotel-booking site you're currently on.
- Page typesearchResults
Tells Vio whether you're viewing search results, a hotel listing, or another page type on the site.
- Hotel you're viewingBeautiful 3 bedroom apartments in Shoreditch
The name of the specific hotel listing shown on the page, reveals exactly which property you're considering.
- Per-install IDb3f2a9de-7c41-4e88-9a2f-114fbb2ad013 (illustrative)
A persistent random ID tied to your extension install, letting Vio link every hotel page you visit into one profile over time.
- Referring extensionlegrooms
Identifies Legrooms+ as the source of the visit so Vio can attribute the referral and pay a commission on the partner's behalf.
The code that does this
Hermes SDK: endpoint config, the site-matcher list, and the tracking call
Endpoint config
vio.jsconst n = { apiBaseUrl: "https://partners.api.vio.com/v1", trackingUrl: "https://fe-evas.fih.io/browser-extension/event", remoteConfigUrl: "https://www.vio.com/js/browser-extension/remote-config/v1/config.json", apiKey: "", trackingKey: String("<redacted>"), version: "1.3.2", options: { debug: false, verboseLogging: false, language: "en-US", fetcher: (...e) => fetch(...e), storage: typeof chrome !== "undefined" && chrome.storage !== undefined ? chrome.storage : { sync: { get: async () => Promise.resolve({}), set: async () => Promise.resolve(), remove: async () => Promise.resolve(), clear: async () => Promise.resolve() }, local: { get: async () => Promise.resolve({}), set: async () => Promise.resolve(), remove: async () => Promise.resolve(), clear: async () => Promise.resolve() } } }, update(e) { Object.assign(this, e) }}Site-matcher list (37 patterns)
vio.jsgetAppConfigByKey("hermes_matcher_regexes", [{ regex: "https://.*tripadvisor.*", flags: ""}, { regex: "https://.*kayak.*", flags: ""}, { regex: "https://.*expedia.*", flags: ""}, { regex: "https://.*booking.*", flags: ""}, { regex: "https://.*hotel.*", flags: ""}, { regex: "https://.*hoteles.*", flags: ""}, { regex: "https://.*tripadvisor.*", flags: ""}, { regex: "https://.*expedia-aarp.*", flags: ""}, { regex: "https://.*expediataap.*", flags: ""}, { regex: "https://.*travelocity.*", flags: ""}, { regex: "https://.*orbitz.*", flags: ""}, { regex: "https://.*cheaptickets.*", flags: ""}, { regex: "https://.*ebookers.*", flags: ""}, { regex: "https://.*wotif.*", flags: ""}, { regex: "https://.*lastminute.*", flags: ""}, { regex: "https://carsandstays.delta.*", flags: ""}, { regex: "https://vacations.alaskaair.*", flags: ""}, { regex: "https://*.priceline.com", flags: ""}, { regex: "https://*.marriott.*", flags: ""}, { regex: "https://.*hilton.*/en/book/reservation.*", flags: ""}, { regex: "https://.*hilton.*/en/search.*", flags: ""}, { regex: "https://.*accor.*", flags: ""}, { regex: "https://.*agoda.*", flags: ""}, { regex: "https://.*caesars.*/book/(.*/hotel.*|room-list.*)", flags: ""}, { regex: "https://.*caesars.*/book/(search|hotel-list.*)", flags: ""}, { regex: "https://.*choicehotels.*/(reservations/.*|.*-hotels/.*)", flags: ""}, { regex: "https://.*choicehotels.*/(reservations/hotel-list.*|regional-hotels.*)", flags: ""}, { regex: "https://.*hyatt.*/shop/.*", flags: ""}, { regex: "https://.*hyatt.*/(explore-hotels/map.*|search/hotels/.*)", flags: ""}, { regex: "https://.*ihg.*/hotels/.*/(hoteldetail.*|find-hotels/select-roomrate.*)", flags: ""}, { regex: "https://.*ihg.*/hotels/.*/(reservation.*|find-hotels/hotel-search.*)", flags: ""}, { regex: "https://.*mgmresorts.*/(en/hotels/.*|book-room/room/.*)", flags: ""}, { regex: "https://.*mgmresorts.*/(en/hotels.html.*|book-room/resort/.*)", flags: ""}, { regex: "https://.*trip.com/hotels/detail.*", flags: ""}, { regex: "https://.*trip.com/hotels/list.*", flags: ""}, { regex: "https://.*wyndhamhotels.*/(wyndham/.*|.*/rooms-rates.*)", flags: ""}, { regex: "https://.*wyndhamhotels.*/(hotel-search.*|hotels/.*)", flags: ""}])track() — builds and sends the event
vio.jsasync track(e) { const t = [e.category, e.entity, e.action].filter(Boolean).join("_"); return n.options.fetcher(n.trackingUrl, { headers: { accept: "*/*", "content-type": "application/json", "x-api-key": n.trackingKey }, method: "POST", body: JSON.stringify({ properties: { ...e, anonymousId: this.anonymousId, name: t } }) })}Where the tracking data goes
- fe-evas.fih.io
Vio.com's tracking-event ingestion endpoint. Receives the page/hotel context payload shown above, tagged with the Legrooms+ affiliate ID, confirmed by traffic capture.
- partners.api.vio.com
Vio.com's hotel-search API. The SDK is coded to POST check-in/checkout dates, guest counts, and prices here on a matched page; it did not fire in our test.
- www.vio.com
Serves the remote config that lists which site URL patterns trigger tracking (hermes_matcher_regexes), Vio can change the matched-site list without an extension update.
Extension sends page contents and your login details to a vendor frame
On request from a vendor frame on some sites, it sends the page HTML, your login token and chosen stored data to it, and can tick or click items the server picks.
What actually happens
A matching site loads a roomunlocker.com popup iframe that sends a ta_html_request message.
The extension can tick or click a configured element, then reply with page HTML, account data and storage values.
Values posted into the popup iframe
- Page HTMLdocument.body.innerHTML
The full body markup of the page you are viewing.
- Extension tokenpayload.token
The extension's own sign-in token.
- Account objectpayload.account
Your extension account details.
- Configured storage keys{"userState": "..."}
Browser storage values for keys named by the remote config.
The code that does this
Message handler in content.js
else if ("ta_html_request" === a.data) { (null == h ? void 0 : h.preProcessAction) && (yield(y = h.preProcessAction, r(void 0, void 0, void 0, (function*() { const e = document.querySelector(y.selector); return !!e && ("check" === y.action && e instanceof HTMLInputElement ? e.checked || (e.checked = !0, e.dispatchEvent(new Event("change", { bubbles: !0 }))) : "click" === y.action && e.click(), y.waitAfterAction && (yield new Promise((e => setTimeout(e, y.waitAfterAction)))), !0) })))); let e = {}; if (null == h ? void 0 : h.storageData) { const t = "localStorage" === h.storageData.type ? localStorage : sessionStorage; e = h.storageData.keys.reduce(((e, n) => (e[n] = t.getItem(n), e)), {}) } "aa" === (null == h ? void 0 : h.id) && (e = Object.assign(Object.assign({}, e), { userState: sessionStorage.getItem("userState") })), "flightConfirmations/aa/confirmPage" === (null == h ? void 0 : h.id) && (e = Object.assign(Object.assign({}, e), e.userState ? {} : { userState: localStorage.getItem("userState") })); const a = yield r(void 0, void 0, void 0, (function*() {Iframe destination
- roomunlocker.com
Vendor domain serving the popup iframe that receives the posted page data.
Observation
Static analysis finding. This behaviour was identified by reading the shipped extension code and has not yet been reproduced in a live run. The trigger conditions and the exact data sent are read from the code, not from an observed capture.
Legrooms+ sends Amazon order details and your account email to Rokt
Code analysis shows that on Amazon order pages the extension reads the order ID and total, and in a remote-config test group your email, and passes them to Rokt.
What actually happens
You land on an Amazon order confirmation page while in the remote-config test group.
The extension reads the order ID and total and hands them, plus your email if enabled, to the Rokt SDK.
Attributes built for Rokt
- Account emailjane.doe@example.com (illustrative)
Your extension account email, sent only in the QA arm or when sendEmail is on.
- Order total84.17
The order total read from the confirmation page.
- Order reference113-4821907-5530642 (illustrative)
The Amazon order ID from the page URL or text.
- Country and languageUS, en
Locale details of your session.
The code that does this
Attribute builder and Rokt call
}, t.primaryLanguage = L, t.buildRoktAttributes = function(e) { var t; const n = {}, r = "string" == typeof e.email ? e.email.trim().toLowerCase() : ""; r && r.length <= 254 && A.test(r) && (n.email = r); "number" == typeof e.totalPrice && Number.isFinite(e.totalPrice) && e.totalPrice > 0 && (n.totalprice = Math.round(100 * e.totalPrice) / 100); const a = (null !== (t = e.orderRefOf) && void 0 !== t ? t : u)(e.orderRef); a && (n.confirmationref = a); /^[A-Z]{2}$/.test(e.country) && (n.country = e.country); const o = L(e.language); o && (n.language = o); const i = e.legroomExtensionVersion; "string" == typeof i && C.test(i) && (n.legroomextensionversion = i); window.mParticle.ready((function() { Promise.resolve().then((function() { return window.mParticle.Rokt.selectPlacements({ identifier: e.identifier, attributes: n, omitUrl: !0 }) })).then(t, i) })) }));Destinations named in the code
- apps.rokt.com
Rokt placement and identity endpoint called by the bundled SDK.
- apps.roktecommerce.com
Rokt e-commerce endpoint used by the bundled SDK.
Observation
Static analysis finding. This behaviour was identified by reading the shipped extension code and has not yet been reproduced in a live run. The trigger conditions and the exact data sent are read from the code, not from an observed capture.
If you have legrooms+-for-google-flig installed
- Open
chrome://extensionsand turn on Developer mode to show IDs. Find the one with IDnhonfddkgankhjilponlbdccpabaaknpand choose Remove. - Block the servers only it was seen contacting:
fe-evas.fih.io,www.vio.com,api.hermes.vio.com. - Scan your browser to check the rest of your extensions.
legrooms+-for-google-flig version history
11.3.3
Mar 4, 2026
+20 more
12.2.15
Nov 10, 2026
12.2.16
Nov 14, 2026
12.2.17
Nov 14, 2026
Where legrooms+-for-google-flig sends data
- api.travelarrow.io/v3/cashback/…18 calls
From its background script · 1 other extension
- api.travelarrow.io/accounts/…13 calls
From its own pages · 1 other extension
- api.travelarrow.io/cashback/heruistics10 calls
From its background script · 1 other extension
- api.travelarrow.io/cashback/stand-down10 calls
From its background script · 1 other extension
- api.travelarrow.io/metadata10 calls
From its background script · 1 other extension
- api.travelarrow.io/v3/deals10 calls
From its background script · 1 other extension
- api.travelarrow.io/v3/events10 calls
From its background script · 1 other extension
- ip-api.com/json10 calls
From its background script · 15 other extensions
- api.travelarrow.io/accounts6 calls
From its background script · 1 other extension
- api.travelarrow.io/v1/campaigns/…6 calls
From its background script · 1 other extension
- fe-evas.fih.io/browser-extension/event5 calls
From a script it injects into websites · only this extension
- fonts.googleapis.com/css25 calls
From a script it injects into websites · 378 other extensions
- www.vio.com/js/browser-extension/…5 calls
From a script it injects into websites · only this extension
- api.hermes.vio.com/v1/manifest4 calls
From its background script · only this extension
Named inside its requests but not contacted (servers it tested or reported on): expedia.com, kayak.co.uk, www.expedia.com, www.kayak.co.uk.
Chrome Web Store listing
- Versions
- 12.2.17 latest of 24 seen since March 4, 2026
- Store rating
- 2.9 from 114 ratings
- Last updated
- November 17, 2026
- Size
- 2.88 MiB
- Privacy policy
- www.flightlegroom.com
