Is mkeeper safe?
mkeeper is medium risk. Code analysis shows the extension reads the Wildberries buyer token from page storage and posts it to prod.mkeeper.ru. We did not observe this in our test session.…
Who publishes itИП Золотов - no other listings under this identity, 6 shared hostnames
ИП Золотов - no other listings under this identity, 6 shared hostnames
Shared hosts - 6 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.
mkeeper findings
Wildberries buyer token is sent to prod.mkeeper.ru from wildberries.ru pages
Code analysis shows the extension reads the Wildberries buyer token from page storage and posts it to prod.mkeeper.ru.
We did not observe this in our test session.
What actually happens
You open a Wildberries page while signed in as a buyer.
The code reads your buyer token and sends it to prod.mkeeper.ru.
The request carries the extension's license key as its Authorization header.
The code that does this
Background handler that posts the token
sendUserWbxToken handler
background.js// The background script is shipped unminified; the handler above is the readable form.Token read from page storage
mk_main.js// Reads the buyer token from wbx__tokenData in localStorage.Data in the request
- Buyer tokenwbx__tokenData.token (value not captured)
Wildberries buyer session token read from localStorage.
- Validation cookiewbx-validation-key (value not captured)
wbx-validation-key cookie from cmp.wildberries.ru, if present.
- License keykey:key2 (value not captured)
The extension's own license key, sent as Authorization.
Where the data goes
- prod.mkeeper.ru
Endpoint /api/users/user_token/set receives the buyer token.
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.
Extension sends Wildberries supplier data to mkeeper.ru
It captures supplier list data from Wildberries' responses and forwards it, in a simple reversible encoding, to prod.mkeeper.ru.
What actually happens
You use a Wildberries seller page that requests the supplier list.
The extension copies the response and sends it to the vendor's debug endpoint, base64 encoded.
What the request carries
- Supplier list{"suppliers":[{"id":123456,"name":"IP Example"}]} (illustrative)
The seller accounts and metadata returned by the Wildberries API for your login.
- Authorization header<key>:<key2>
The extension's own license key pair, which ties the upload to your Keeper account.
The code that does this
Receiving listener and the send
Page hook names the event
mk_s_wb.js} else if (isSuppliers) { eventName = 'setInteractiveSuppliers';} else if (isConfigValues) {Background handler for the same endpoint
background.jsif (request.message === "setSuppliers") { const url = 'https://prod.mkeeper.ru/api/debugdev/' fetch(url, { method: 'POST', headers: { 'Content-Type': 'application/json', 'Authorization': request.authorization, }, body: JSON.stringify({ data: request.data }) }) return true}Where the data goes
- prod.mkeeper.ru
Vendor backend (MPSTATS Keeper); receives the encoded supplier list at /api/debugdev/.
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.
mkeeper version history
1.22.130
Mar 4, 2026
+41 more
1.29.7
Nov 6, 2026
1.29.8
Nov 10, 2026
1.29.9
Nov 18, 2026
Chrome Web Store listing
- Versions
- 1.29.9 latest of 45 seen since March 4, 2026
- Store rating
- 3.5 from 83 ratings
- Last updated
- November 6, 2026
- Size
- 2.68 MiB
- Privacy policy
- mkeeper.ru
