Is Privacy Extension For WhatsApp Web - wabulk.net safe?
Privacy for WhatsApp Web is medium risk. Once WhatsApp Web loads, the worker requests ad placements from ext.leadsext.com, using the install token from registration. A placement triggers a promo and view/click reports, timezone included. This session captured only the fetch.…
Who publishes itsmallduck - 2 other listings from the same operator, none carrying a finding
smallduck - 2 other listings from the same operator, none carrying a finding
Same store account
2 other listings published from this account, 20k+ users between them, none of them carrying a finding.
Privacy for WhatsApp Web findings
New promo-tracking channel reports your engagement to leadsext.com
Once WhatsApp Web loads, the worker requests ad placements from ext.leadsext.com, using the install token from registration.
A placement triggers a promo and view/click reports, timezone included.
This session captured only the fetch.
What actually happens
You open WhatsApp Web and your session finishes loading.
The background service worker automatically fetches promo placements from ext.leadsext.com and wires up reporting for anything it renders in the page.
The request carries the persistent session token issued when the extension was first installed, so the fetch is tied to your specific installation.
Captured request
200 OK. Body is gzip+base64 encoded JSON that decodes to {"placements":{},"message":"success"}, no placements were returned in this test, so no promo card rendered and no follow-up engagement report fired.
- crx_vcwgjg
- <redacted session token>
- Content-Type
- application/json
{}The code that does this
Placement fetch and engagement-report function, both via the same router and fetch wrapper
getPromotions — the function that fired live during dynamic analysis
assets/chunk-7da65e19.jsconst getPromotions = async () => { try { const result = await (async (cachedPlacementIds = []) => { const response = await fetchWithSessionToken("https://ext.leadsext.com/crx/rtio", { method: "POST", headers: { "Content-Type": "application/json" }, body: cachedPlacementIds.length > 0 ? { placements: cachedPlacementIds } : {} }); if (200 === response.code) { let payload = response.result; if (typeof payload === "string") { const decompressed = gzipHelper.ungzip(payload); payload = decompressed ? JSON.parse(decompressed) : { placements: {} }; } return payload || { placements: {} }; } throw new Error(response.message || "getPromotions failed"); })(); extensionState.setPromoPlacements(result.placements || {}); } catch (e) {}};reportPromotionAction — wired to PROMO_VIEWED/CLICKED/CLOSED, not independently captured on the wire this session
assets/chunk-7da65e19.jsconst reportPromotionAction = async ({ promotionId, displaySessionId, userAction, viewDurationMs }) => { const reportPayload = { promotionId, displaySessionId, userAction, ...(viewDurationMs !== undefined && { viewDurationMs }), userTimezone: Intl.DateTimeFormat().resolvedOptions().timeZone, userLocalTime: (new Date()).toISOString() }; const response = await fetchWithSessionToken("https://ext.leadsext.com/crx/wewfu", { method: "POST", headers: { "Content-Type": "application/json" }, body: { data: gzipHelper.gzipToBase64(JSON.stringify(reportPayload)), rtl: "" } }); if (200 === response.code) { let result = response.result; if (typeof result === "string") result = gzipHelper.ungzip(result) || result; return result; } throw new Error(response.message || "reportPromotionAction failed");};Fields in the engagement report; code path present, not captured on the wire
- How long you viewed the promoviewDurationMs: 4213
The time between the promo appearing and you dismissing or clicking it.
- Your local timezoneuserTimezone: "America/Sao_Paulo"
Read from your browser's Intl settings, this narrows down your general location.
- What you did with the promouserAction: "click"
Whether you viewed, clicked, or closed the promotional content.
- Your install session tokencrx_vcwgjg header (redacted)
The same permanent token used to identify your installation on every other request this extension makes.
Where placement fetches and engagement reports go
- ext.leadsext.com
Extension analytics/promo backend, same host as the install-registration channel; serves placements via /crx/rtio, receives engagement reports via /crx/wewfu.
Remote config from ext.leadsext.com controls DOM selectors and feature flags
On each start, the extension fetches gzip config from ext.leadsext.com/crx/cjj2: 9,400+ chars of JSON stored as dockingInfo.
It sets which DOM selectors target WhatsApp Web, which CSS injects, and which banners show, remotely, no update.
Captured request
- crx_vcwgjg
- <session-token-from-registration>
What's stored on your device
inStor/notLInStor are the selectors the MutationObserver watches; gc/pc set how many ratings trigger a prompt.
{ "dockingInfo": { "gc": 1, "pc": 1, "pss": {}, "email": "support@wabulk.net", "inStor": "div._1jJ70", "webUrl": "https://wabulk.net/", "helpUrl": "https://privacy-wa-web.wabulk.net/help", "notLInStor": "div.x1lliihq canvas", "toolsRedDot": 0 }}Third-party destinations
- ext.leadsext.com
Remote configuration server, delivers feature flags, DOM selectors, CSS rules, and promotional content to all active installations.
Persistent anonymous identifier sent to ext.leadsext.com on install
On install, the extension generates a UUID stored in chrome.storage.sync.
A POST to ext.leadsext.com/crx/in carries that UUID and an OAuth client ID.
The server replies with token crx_vcwgjg, attached to later requests, linking reinstalls.
Captured request
- Content-Type
- application/x-www-form-urlencoded
aid=749905846386-8ntjrq2jnhhh8cjuq3qgro3d67i2sj1q.apps.googleusercontent.com&idStr=wa-privacy&anonCode=ec95b3f05f0a4ad297312c69cf699c97&unicode=3027aaadacba46d3b6c116bf3be7871f×tamp=1780679526814&aiid=749905846386-8ntjrq2jnhhh8cjuq3qgro3d67i2sj1q.apps.googleusercontent.com&idUni=wa-privacy&aCode=ec95b3f05f0a4ad297312c69cf699c97What's stored on your device
Stored in chrome.storage.sync, the key follows the user's Chrome account and resends on any device with the extension.
{ "Y5rD2uBG_ANON_CODE": "ec95b3f05f0a4ad297312c69cf699c97"}Third-party destinations
- ext.leadsext.com
Extension analytics and session management backend, receives install events, anonymous UUIDs, and Google OAuth client ID; issues persistent session tokens.
What Privacy for WhatsApp Web can do
Permissions this extension asks for, as declared in version 3.3.16. 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.3.19, which we have not unpacked yet.
Store data in your browser
storage
See the address and title of every tab you have open
tabs
Store an unlimited amount of data in your browser
unlimitedStorage
Privacy for WhatsApp Web version history
3.3.16
Mar 4, 2026
3.3.17
Jul 21, 2026
3.3.18
Jul 28, 2026
3.3.19
Aug 2, 2026
Where Privacy for WhatsApp Web sends data
- ext.leadsext.com/crx/uuinf6 calls
From its background script · 1 other extension
- ext.leadsext.com/crx/cjj25 calls
From its background script · 1 other extension
- ext.leadsext.com/crx/rtio3 calls
From its background script · 1 other extension
- ext.leadsext.com/crx/in2 calls
From its background script · 1 other extension
Named inside its requests but not contacted (servers it tested or reported on): 749905846386-8ntjrq2jnhhh8cjuq3qgro3d67i2sj1q.apps.googleusercontent.com.
Chrome Web Store listing
- Versions
- 3.3.19 latest of 4 seen since March 4, 2026
- Store rating
- 4.7 from 13,592 ratings
- Last updated
- August 1, 2026
- Size
- 1.46 MiB
- Privacy policy
- check-wa-number.wabulk.net
