Ransomware Tracker by ExposureDrift
Dashboard / Victims / MJets

MJets was listed on 04 July 2025 by the incransom ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). incransom listed 58 organizations that month and 1045 in total.

  • Listed 504 days ago.
  • 542 organizations were listed by all groups in July 2025, see the month.
  • 16 in Transportation that month.
  • 5 in TH that month.

Updated 2026-11-19 06:03 UTC. Data: public leak-site listings. How we work.

MJets corporate emblem
Listed by incransom Disclosed: 2025-08-15 20:20 UTC

MJets

mjets.com Transportation TH

Threat Group Post & Evidence

Listed by
INC Ransom 1,045 listings in total

The listing states no data size and no ransom demand.

No capture of the original post

We only show a screenshot when we captured the group's own page ourselves. For this listing we have not, so none is shown.

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.

MJets was founded in 2007 thanks to the visionary partnership between William E. Heinicke, an aviation enthusiast with an unquenchable passion for flying, and Kirith Shah, one of Thailand's most respected businessmen. By 2010, we had already made our mark in aviation history by becoming pioneers in the field of fixed-base operations (FBO) in Thailand. The database contains the personal data of more than 1500 people, financial information, and other internal files belonging to MJets.

Kinds of data mentioned

  • Databases and backups

    “…pioneers in the field of fixed-base operations (FBO) in Thailand. The database contains the personal data of more than 1500 people, financial information, and other internal…”

Plain-English summary AI-written

The group says it holds an MJets database containing personal data for more than 1,500 people, financial information, and other internal 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 MJets (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 MJets 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 MJets 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.
  • Check software and integrations you take from them If you run their software or call their API, check that updates come through the usual channel and rotate the keys and tokens you hold for it. Why: The post names: databases and backups.

Within 30 days

  • Keep watching MJets 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 MJets

Within 3 days

  • Rotate database and cloud access Rotate database and cloud-storage keys, review public bucket and snapshot sharing, turn on object-level audit logging and keep backup encryption keys separate. Why: The post names: databases and backups.
  • Lock down exposed admin, VPN and SSO panels Restrict by IP allow-list or a zero-trust proxy and require MFA. Why: A passive scan found 1 critical panel(s) reachable from the internet.
  • Check regulatory and stakeholder notification duties No country is recorded for this listing. Identify the data-protection and contractual duties that apply where the affected people live, and ask counsel. General guidance, not legal advice. Why: The listing records no country.

Within 30 days

  • Check shared suppliers and software List the suppliers and software you share with other Transportation organizations and ask them whether they were affected. Why: incransom listed 6 other Transportation 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

Resolved Domain mjets.com
Industry Vertical Transportation
Country TH
Enrichment Status ENRICHED

Listing severity score (heuristic)

79/100 • ELEVATED

A heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.

1. Sector Criticality 20/30 pts
Transportation and logistics
2. Group tier 25/25 pts
Tier 1: among the groups with the most listings in our data
3. Data Volume & PII Scope 18/25 pts
Larger claim: gigabytes, or business or financial records named in the post
Formula: sector • group tier • data claimed (scaled to 100) Rule-based score

External Attack Surface Profile

ASM Intelligence
75/100 • CRITICAL
Last Audited: 2026-11-14 17:36 UTC Passive Recon
Total Network Assets 17
5 hosts • 12 unique IPs
0 cloud-hosted • 2 SaaS
Subdomain Assets 5
Critical Panels 1 (VPN/Admin/SSO)
Non-Prod / UAT 0 Staging/Dev
SaaS Ecosystem 2 Cloud Apps
Primary CSP Public Cloud / E
Email Security Grade A (SPF/DMARC)
Open the full attack surface scan →
Is Your Organization Exposed?

Run a free passive scan on your own domain to see what an attacker can see from the outside.

Defense Telemetry

Passive DNS
Mail Gateway Microsoft 365 / Exchange Online
DNS Authority Authoritative DNS (com)
Edge CDN / Shield None
SPF Record Configured
DMARC Policy Enforced
Public DNS records only • no port scanning

More Claims by incransom

All →
Boeing
Government & Defense 2026-11-20 03:46 UTC
CHAMBOURCY
Agriculture and Food Production 2026-11-19 17:35 UTC
Pulsar
Technology 2026-11-19 01:56 UTC
CENTERED CO., LTD.
Technology 2026-11-19 01:56 UTC
Chin Fong Machine Industrial
Manufacturing 2026-11-17 00:14 UTC
pilotcat.com
Technology 2026-11-16 22:40 UTC