Is AT Price Tracker (Working June 2026) safe?

Low risk

AT Price Tracker (Working June 2026) is low risk.

AT Price Tracker reads the user's signed-in Google account email and sends it with every scraped vehicle listing to its own servers.

On first use, the extension's background service worker calls Chrome's identity API to obtain the user's signed-in Google account email without any consent screen, then stores it and attaches it to every subsequent request sent to at.liprock.com. Each time a tracked Autotrader listing page is scraped, the extension sends the page URL, vehicle ID, and the account email to this server, and it can also be remotely instructed to pull the value of a specific element from the page and send that along too.

Liprockv1.20.1Extension ID cbecfdegmcppmbpbffdpagongfpbohmdChrome Web Store
24Risk
AI-assisted analysis.

AT Price Tracker (Working June 2026) findings

Autotrader extension sends a link chosen by a remote selector to at.liprock.com

MediumunwantedCWE-200Static analysis

Code analysis shows a selector from at.liprock.com settings picks a page element whose link is sent back with your email.

What actually happens

You did this

at.liprock.com returns a settings object with a base64 selector in field a.m.

The extension did this

The page script reads the link of the matching element and sends it with the vehicle id and your email.

The code that does this

Selector-driven link read

Readable version
// contentScript.min.js; d = config.a.m, a base64 selector from /api/v2/wif (d && document.querySelector(atob(d))) {  const href = document.querySelector(atob(d)).getAttribute("href");  if (href) {    chrome.runtime.sendMessage({      type: "fR", route: "m",      user: await getUser(),      data: { e: vehicleId, m: btoa(href) },      url: window.location.href    });  }}

Why you can't catch this in DevTools

The selector arrives base64-encoded in the settings response, so the target element is not visible in the shipped code.

Decoded value
[data-gui="dealer-website-button"], [data-testid="visit-retailer-website"]

Where the data goes

    • at.liprock.com

    Vendor backend serving the selector config and receiving the link, vehicle id and email.

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.

Autotrader extension reads your Chrome email and sends it to at.liprock.com

MediumunwantedCWE-359Static analysis

Code analysis shows the extension reads the Chrome profile email on the first price check and sends it to at.liprock.com with each listing.

What actually happens

You did this

You open a vehicle listing on autotrader.co.uk.

The extension did this

The extension reads your Chrome profile email and attaches it to the listing data it sends to at.liprock.com.

Fields in each vehicles POST

  • Account email
    jane.doe@example.com

    Ties each listing check to your Google account.

  • Listing URL
    https://www.autotrader.co.uk/car-details/202401012345678

    Shows which car you are looking at.

  • Vehicle ID
    202401012345678

    Identifies the listing and its price.

The code that does this

Email lookup on first contact

Readable version
// background.min.js, handler for message type "getUserInfo"const stored = await chrome.storage.local.get(["email"]);if (stored.email) {  respond(stored);} else {  chrome.identity.getProfileUserInfo(info => {    if (info && info.email) chrome.storage.local.set({ email: info.email });    respond(info);  });}

Where the data goes

    • at.liprock.com

    Vendor backend receiving listing URL, vehicle id and account email.

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.

What AT Price Tracker (Working June 2026) can do

Permissions this extension asks for, as declared in version 1.13.4. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to. The current listed version is 1.20.1, which we have not unpacked yet.

  • Sign you in with your Google account

    identity

  • See the email address of your Google account

    identity.email

  • Store data in your browser

    storage

AT Price Tracker (Working June 2026) version history

  1. 1.13.4

    Mar 4, 2026

  2. +5 more

  3. 1.19.0

    Oct 10, 2026

  4. 1.20.0

    Nov 3, 2026

  5. 1.20.1

    Nov 3, 2026

Where AT Price Tracker (Working June 2026) sends data

  • at.liprock.com/api/v2/…7 calls

    From its own pages · also found in its code · only this extension

Chrome Web Store listing

Versions
1.20.1 latest of 9 seen since March 4, 2026
Store rating
4.9 from 1,610 ratings
Last updated
June 2, 2026
Size
488 KiB
Privacy policy
at.liprock.com
Updated November 20, 2026