Native Touch Inc. was listed on 05 November 2026 by the N0n ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). N0n listed 229 organizations that month and 397 in total.
- Listed 14 days ago.
- 984 organizations were listed by all groups in November 2026, see the month.
- 152 in Technology that month.
- 54 in CA that month.
Updated 2026-11-19 05:29 UTC. Data: public leak-site listings. How we work.
Native Touch Inc.
Threat Group Post & Evidence
- Listed by
- N0n 397 listings in total
The listing states no data size and no ransom demand.
Dark Web Leak Proof Screenshot
Original Source (Safe Tor Stream)The group's leak-site address is on paid plans
Free accounts see who listed this organization, when, and what the post claims. The address of the group's own page is shown to license-key holders. If you have a key, see what a license key adds.
What the group says it holds
Taken from the group's own post. Ransomware Tracker by ExposureDrift has not seen the data and cannot confirm any of this.
mobile advertising and audience data · Canada | The consumer audience data assets of a Canadian mobile advertising company: device movement records for Canadian consumers at multibillion record scale, each carrying device advertising identifiers, coordinates and IP addresses; Location ping records with device advertising identifiers, precise coordinates, carriers and IP addresses; Consumer IP geolocation tables at billion row scale mapping IP addresses to cities, postal codes, coordinates and internet providers; Live ad serving logs through October 2026 carrying consumer IP addresses, device advertising identifiers and coordinates; Device intelligence files received from the company's telecom data partner, and partner audience delivery records; The company's platform user directory with staff and client agency accounts, and its platform configuration records | [NOT PAID — EXPOSED] Initia…
Show the full post (963 characters)
mobile advertising and audience data · Canada | The consumer audience data assets of a Canadian mobile advertising company: device movement records for Canadian consumers at multibillion record scale, each carrying device advertising identifiers, coordinates and IP addresses; Location ping records with device advertising identifiers, precise coordinates, carriers and IP addresses; Consumer IP geolocation tables at billion row scale mapping IP addresses to cities, postal codes, coordinates and internet providers; Live ad serving logs through October 2026 carrying consumer IP addresses, device advertising identifiers and coordinates; Device intelligence files received from the company's telecom data partner, and partner audience delivery records; The company's platform user directory with staff and client agency accounts, and its platform configuration records | [NOT PAID — EXPOSED] Initially listed anonymously by N0n as "Company #137" on 2026-11-05.
Kinds of data mentioned
-
Customer or client data
“…delivery records; The company's platform user directory with staff and client agency accounts, and its platform configuration records | [NOT PAID — EXPOSED] Initially listed…”
-
Employee and HR records
“…audience delivery records; The company's platform user directory with staff and client agency accounts, and its platform configuration records | [NOT PAID — EXPOSED]…”
Plain-English summary AI-written
The group says it holds Canadian mobile advertising audience data, including device movement records, location pings, IP geolocation tables, live ad-serving logs, and device intelligence files.
Written by an AI model (openai/gpt-6-luna) from the post above. It can contain mistakes: rely on the quote, not the summary.
What to do about this listing
Choose who you are. Each step shows why it appears and, where we have one, its source. General guidance, not legal or incident-response advice.
If you work with Native Touch (customer, supplier or partner)
Within 3 days
- Do not open the group's page or download the data Do not visit the leak site or download files from a listing. Holding stolen data can be unlawful, and the files can carry malware. Wait for the company's own notice. Why: A safety rule for any leak listing.
- Ask Native Touch directly Write to your contact and ask whether your data, or your access to their systems, is in scope, and ask for a written statement. Your contract or data-protection law may oblige them to tell you if your data is affected: check the notification clause. Why: A listing is only the group's claim; the company is the one who can confirm what was taken.
- Review what Native Touch can reach of yours List the accounts, API keys, VPN or SSO connections and shared mailboxes this company has with you. Rotate the keys you gave them and remove access they do not need. Why: Access a supplier holds is how a listing about them can become a problem for you.
- Expect convincing phishing Messages that quote real orders, invoices or names are more likely after a leak. Tell finance and the help desk to treat any request from, or about, this company with extra care. Why: The post names: customer or client data, employee and hr records.
Within 30 days
- Keep watching Native Touch A supplier's listing can change after the first sighting: the group can add data, change the status or publish. Add the company to your supplier list to be told, and check your own domain too. Why: A listing is a moving claim, not a single event. Add to your supplier list Check your own domain
If you are Native Touch
First 24 hours
- Reset credentials and sessions Force password, API-key and session-token resets for the accounts the post suggests were exposed, enforce phishing-resistant MFA, and revoke OAuth/SSO grants issued before the listing date. Why: The post names: customer or client data.
Within 3 days
- Support affected individuals Identify the employees or customers whose identity data may be in scope and offer identity-protection or credit monitoring; brief the help desk on likely phishing. Why: The post names: employee and hr records.
- Check regulatory and stakeholder notification duties Canada: PIPEDA requires reporting breaches that pose a real risk of significant harm, as soon as feasible. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: Canada.
Within 30 days
- Check shared suppliers and software List the suppliers and software you share with other Technology organizations and ask them whether they were affected. Why: N0n listed 71 other Technology organization(s) in the last 90 days.
General readiness for any ransomware claim (not about this listing)
- Offline, immutable backups and a restore drill Keep backups outside domain-admin reach and practise a restore; a leak does not remove the risk of re-encryption. Why: General practice for any ransomware claim; not specific to this listing.
- Look for mass file access and unusual outbound transfers Review EDR, proxy and identity logs for bulk reads, archive creation and large uploads to file-sharing services. Why: General practice for any ransomware claim; not specific to this listing.
- Phishing-resistant MFA on remote access Enforce MFA on VPN, SSO and admin panels, and retire password-only or SMS-based remote access. Why: General practice for any ransomware claim; not specific to this listing.
Listing details
Listing severity score (heuristic)
50/100 • GUARDEDA heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.
External Attack Surface Profile
ASM IntelligenceNo scan has been run for this domain yet, so there are no figures to show. Running one is passive: it reads public DNS and certificate records only.
Launch Attack Surface Recon →Run a free passive scan on your own domain to see what an attacker can see from the outside.