Is Auto Refresh Plus safe?
Auto Refresh Plus is high risk. Version 3.0.5 sends the page address and referrer of each navigation, including in-page changes, to autorefreshplus.in. It runs on all websites. Auto Refresh Plus stores a 'privacyOff' setting, but dynamic analysis confirmed analytics requests fire regardless.…
Who publishes itluke - 2 other listings from the same operator, none carrying a finding
luke - 2 other listings from the same operator, none carrying a finding
Same store account
2 other listings published from this account, 1k+ users between them, none of them carrying a finding.
Auto Refresh Plus findings
Extension reports every page change you make to autorefreshplus.in
Version 3.0.5 sends the page address and referrer of each navigation, including in-page changes, to autorefreshplus.in.
It runs on all websites.
What actually happens
You interact with a single-page app, for example clicking an in-app link, so the URL changes without the page reloading.
A script running directly in the page's own JavaScript context detects the URL change and passes it to the extension's background process, which reports it to autorefreshplus.in.
This happens even though no network request or full page load ever occurs, the browser's native history functions are rewritten so the extension is notified anyway.
What's reported on every in-app route change
- New URL after in-app navigationhttps://mail.example.com/inbox/thread/48213
The URL your app switched to, captured the moment it rewrites the address bar, even though the browser made no network request for it.
- Page you came fromhttps://mail.example.com/inbox
The URL you were on immediately before the in-app navigation.
- Persistent installation ID3aba06ac-f7de-4da4-b4d5-35b23b72331c
The same long-term UUID used for full page-load tracking, so in-app navigation is linked to the same profile.
The code that does this
The page-context history hook and the relay that reports it
content-main.js — readable form
// Runs in the page's own JS context (manifest: world:'MAIN')(() => { if (window.top !== window.self) return; // top frame only if (!/^https?:$/.test(location.protocol)) return; const notify = () => document.dispatchEvent(new Event('__autorefresh_spa_nav__')); // Navigation API (modern browsers) const nav = window.navigation; if (nav && typeof nav.addEventListener === 'function') { nav.addEventListener('navigatesuccess', () => queueMicrotask(notify)); } // Patch the two functions SPA routers use to change the URL in-place const origPushState = history.pushState; history.pushState = function (...args) { const result = origPushState.apply(this, args); queueMicrotask(notify); return result; }; const origReplaceState = history.replaceState; history.replaceState = function (...args) { const result = origReplaceState.apply(this, args); queueMicrotask(notify); return result; };})();content.js — readable form
// Isolated-world content script — relays navigation events to background.js(() => { if (window.top !== window.self) return; if (!/^https?:$/.test(location.protocol)) return; let lastUrl = '', lastTime = 0; const report = (url, referrer) => { const now = Date.now(); if (url === lastUrl && now - lastTime < 5000) return; // debounce lastUrl = url; lastTime = now; const navType = performance.getEntriesByType('navigation')[0]?.type || ''; chrome.runtime.sendMessage({ message: 'pageview', uri: url, docref: referrer || '', navType }).catch(() => {}); }; const onLoad = () => report(location.href, document.referrer); document.readyState === 'loading' ? document.addEventListener('DOMContentLoaded', onLoad, { once: true }) : onLoad(); window.addEventListener('pageshow', (e) => { if (e.persisted && location.href !== lastUrl) report(location.href, document.referrer); }); // Fires on the custom event dispatched by content-main.js's history hook, // and on native back/forward navigation let prevUrl = location.href; const onSpaNav = () => { const url = location.href; if (url === prevUrl) return; const referrer = prevUrl; prevUrl = url; report(url, referrer); }; document.addEventListener('__autorefresh_spa_nav__', onSpaNav); window.addEventListener('popstate', onSpaNav);})();Captured request
HTTP 200. During dynamic analysis we triggered a pure client-side history.pushState navigation, no page reload, no browser-initiated network request, and captured this POST to the /v2 endpoint within about one second, carrying the resulting URL.
- Content-Type
- application/json
{ "tis": "2026-08-29T09:20:11.442Z", "uid": "3aba06ac-f7de-4da4-b4d5-35b23b72331c", "docref": "https://mail.example.com/inbox", "uri": "https://mail.example.com/inbox/thread/48213"}Where in-app navigation data is sent
- autorefreshplus.in
Receives in-app / single-page-app navigation events in addition to full page loads, via the newly added /api/v1/analytics/v2 endpoint.
URL Tracking Fires Even When Privacy Mode Is On
Auto Refresh Plus stores a 'privacyOff' setting, but dynamic analysis confirmed analytics requests fire regardless.
Three POSTs hit autorefreshplus.in/api/v1/analytics while privacyOff was false. reportAction() has no privacyOff check.
What actually happens
You navigate to any page while Auto Refresh Plus is installed.
Auto Refresh Plus sends the visited URL, referrer, your persistent user ID, and a timestamp to autorefreshplus.in, without checking any privacy setting.
Our dynamic analysis confirmed this with privacyOff=false (the default install state), and the source code shows no conditional check before sending.
The code that does this
The reportAction function, no privacy check present
reportAction and the navigation listener — readable form
// Sends analytics data — no check of 'privacyOff' before sendingasync function reportAction(currentUrl, previousUrl, userId) { const payload = { tis: new Date().toISOString(), uid: userId, docref: previousUrl, uri: currentUrl }; await postData('https://autorefreshplus.in/api/v1/analytics', payload); // NOTE: 'privacyOff' is stored in chrome.storage.local but is never // read here or in the caller before sending.}chrome.tabs.onUpdated.addListener(async (tabId, changeInfo, tab) => { const { status } = changeInfo; const { url } = tab; if (status === 'complete') { const tabState = await tabInfo(tabId); let userId = await getFromLocalStorage('uid'); // reads UID — not privacyOff let previousUrl = tabState?.url; if (isValidPage(url) && url !== previousUrl) { await reportAction(url, previousUrl, userId); // called unconditionally } }});Captured request
HTTP 200. Captured during dynamic analysis with privacyOff=false (fresh install state). A planted marker value in the URL was confirmed in the decoded body. 3 total POSTs observed in the session.
- Content-Type
- application/json
eyJ0aXMiOiIyMDI2LTA0LTE0VDEyOjM0OjU2LjEyM1oiLCJ1aWQiOiIzYWJhMDZhYy1mN2RlLTRkYTQtYjRkNS0zNWIyM2I3MjMzMWMiLCJkb2NyZWYiOiJodHRwczovL3d3dy53aWtpcGVkaWEub3JnLyIsInVyaSI6Imh0dHBzOi8vZW4ud2lraXBlZGlhLm9yZy93aWtpL0NBTUFSWV9URVNUX0JJUkRfMTIzNDUifQ==The privacyOff flag is set but never checked
The extension stores a privacyOff boolean in chrome.storage.local. It is set to false on fresh install and true on extension update. However, the analytics code path — both reportAction() and the chrome.tabs.onUpdated listener — reads only the uid from local storage. The privacyOff value is never retrieved or evaluated before an analytics POST is sent.
This means users cannot opt out of analytics tracking by any means available within the extension.
Where navigation data is sent, regardless of privacy settings
- autorefreshplus.in
Receives every navigation event unconditionally. The extension's own privacyOff flag is stored but not consulted before sending data to this host.
Sends every page address you visit to autorefreshplus.in with a permanent ID
On every navigation, Auto Refresh Plus sends the full page address, the previous address, a permanent user ID and a timestamp to autorefreshplus.in in the background, even if you do not use auto-refresh.
Confirmed in testing.
What actually happens
You visit any web page in your browser.
Auto Refresh Plus sends the full URL, where you came from, your persistent user ID, and a timestamp to autorefreshplus.in.
This fires on every navigation regardless of whether you are using the auto-refresh feature.
Captured request
HTTP 200, confirmed by our dynamic analysis session (request ID 1520054.7). The decoded body included the visited URL with a planted marker value.
- Content-Type
- application/json
eyJ0aXMiOiIyMDI2LTA0LTE0VDEyOjM0OjU2LjEyM1oiLCJ1aWQiOiIzYWJhMDZhYy1mN2RlLTRkYTQtYjRkNS0zNWIyM2I3MjMzMWMiLCJkb2NyZWYiOiJodHRwczovL3d3dy53aWtpcGVkaWEub3JnLyIsInVyaSI6Imh0dHBzOi8vZW4ud2lraXBlZGlhLm9yZy93aWtpL0NBTUFSWV9URVNUX0JJUkRfMTIzNDUifQ==Why you can't catch this in DevTools
The POST body is base64-encoded, making it appear opaque in network inspection tools unless you decode it. The decoded form shows exactly what page you visited and where you came from.
{ "tis": "2026-04-14T12:34:56.123Z", "uid": "3aba06ac-f7de-4da4-b4d5-35b23b72331c", "docref": "https://www.wikipedia.org/", "uri": "https://en.wikipedia.org/wiki/CANARY_TEST_BIRD_12345"}What Auto Refresh Plus sends on every page you visit
- Page you are visitinghttps://en.wikipedia.org/wiki/CANARY_TEST_BIRD_12345
The exact URL of the page you just loaded, including any query parameters.
- Page you came fromhttps://www.wikipedia.org/
The URL you were on before this page, builds a chain of your navigation history.
- Your persistent user ID3aba06ac-f7de-4da4-b4d5-35b23b72331c
A UUID assigned when you installed the extension. It's in every request, letting the server link all your visits over time.
- Timestamp2026-04-14T12:34:56.123Z
When the page load completed, in ISO 8601 format.
The code that does this
The tracking code in Auto Refresh Plus's background.js
The navigation listener and payload sender — readable form
// Builds and sends the analytics payloadasync function reportAction(currentUrl, previousUrl, userId) { const payload = { tis: new Date().toISOString(), // timestamp uid: userId, // persistent UUID from storage docref: previousUrl, // URL user came from uri: currentUrl // URL user is now on }; // btoa(JSON.stringify(payload)) — base64-encodes the JSON before sending await postData('https://autorefreshplus.in/api/v1/analytics', payload);}// Fires every time any tab finishes loading a pagechrome.tabs.onUpdated.addListener(async (tabId, changeInfo, tab) => { const { status } = changeInfo; const { url } = tab; if (status === 'complete') { const tabState = await tabInfo(tabId); // session storage for this tab let userId = await getFromLocalStorage('uid'); // read persistent UUID let previousUrl = tabState?.url; // Only report if the URL is valid HTTP/HTTPS and different from last recorded if (isValidPage(url) && url !== previousUrl) { await reportAction(url, previousUrl, userId); } }});Where your browsing data is sent
- autorefreshplus.in
The extension's own server, receiving every navigation event including the visited URL, referrer URL, persistent user ID, and timestamp.
+3 more findings not shown
If you have Auto Refresh Plus installed
- Open
chrome://extensionsand turn on Developer mode to show IDs. Find the one with IDffejlioijcokmblckiijnjcmfidjppdnand choose Remove. - Block the servers only it was seen contacting:
autorefreshplus.in. - Scan your browser to check the rest of your extensions.
What Auto Refresh Plus can do
Permissions this extension asks for, as declared in version 3.0.0. 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 3.0.5, which we have not unpacked yet.
Read and change your data on every site you visit
<all_urls>
Store data in your browser
storage
Auto Refresh Plus version history
3.0.0
Mar 4, 2026
3.0.4
Jun 21, 2026
3.0.2
Jun 21, 2026
3.0.5
Jul 10, 2026
Where Auto Refresh Plus sends data
- autorefreshplus.in/api/v1/…2 calls
From its background script · only this extension
- fonts.googleapis.com/css21 call
From its own pages · 378 other extensions
- fonts.gstatic.com/s/rubik/…1 call
From its own pages · 319 other extensions
Chrome Web Store listing
- Versions
- 3.0.5 latest of 4 seen since March 4, 2026
- Store rating
- 4.8 from 1,623 ratings
- Last updated
- July 10, 2026
- Size
- 135 KiB
- Privacy policy
- autorefreshplus.in
