Skip to main content

Hit by ransomware? Isolate affected systems now. Do not reboot or reformat.

SheMo Noransom舍末无勒

Ransomware family

n0n Ransomware Decryption & Data Recovery

  • Active
  • High
  • No public decryptor

n0n is a data-theft extortion crew that appeared in September 2026. It does not encrypt files; it pressures victims with timed exposure on a dark web leak site. On 12 October it posted 38 port, terminal and shipping organisations across 18 countries and territories in one batch - 12 in South Korea, others in mainland China, Hong Kong and Taiwan - with demands of $2.4M to $14M. As of 21 October it led all groups in leak-site postings for the month.

First seen
2026-09
File extensions
No public information
Ransom notes
No public information
Affected platforms
Windows

Family profile

File extensions
No public information
Ransom notes
No public information
Contact patterns
  • Dark web leak site with a page per victim, marked pending exposure, not paid and exposed, or honored
  • Bitcoin payment to a unique address per victim, verified on-chain by the site
  • A 10% "entry fee" opens a private negotiation room, keyed to the payment's transaction ID
Aliases / versions
N0n、n0n Group、n0n 勒索团伙
First seen
2026-09
Status
Active
Operational status
Newly emerged
Threat level
High
Affected platforms
  • Windows
Tags
  • Emerging
  • Active
  • Extortion-only
  • Supply chain
Decryptor
No public decryptor

n0n is a data-theft extortion crew. As of 2026-10-21 no public report has observed it encrypting files, so there is nothing to decrypt. SOCRadar describes it as avoiding traditional ransomware deployment and making money from stolen data and public pressure.

If encrypted files do appear in your environment, they most likely belong to another family or to separate tooling dropped by the same intruder; identify them from real samples rather than applying this page.

Overview

SOCRadar describes n0n as a financially motivated data-theft extortion group that emerged in September 2026, likely based in Russia. Before the October wave it had posted 21 victims across 17 countries in investment, telecoms, retail, education and pharmaceuticals.

The 12 October maritime batch. n0n posted 38 organisations at once: container terminals and port operators, port IT, EDI and terminal-system providers, shipping lines and ship operators, agencies and logistics firms, plus adjacent crane and steel companies, across 18 countries and territories. South Korea accounted for the most, 12; the list also includes port and shipping organisations in mainland China, Hong Kong and Taiwan. The whole batch was set to be exposed on 19 October at 13:27 UTC, unlike the staggered deadlines the group used before. Demands reviewed by SOCRadar ranged from $2.4 million to $14 million.

Scale. According to HackerFeeds, by 21 October n0n had posted 125 victims for the month - 17.4% of all postings, more than any other group.

Reliability. When SOCRadar published, none of the listed maritime organisations had publicly confirmed a breach, and earlier claims against several well-known companies had not been confirmed by those companies either. Leak-site numbers are the group's own claims, not verified intrusions.

How to identify it

n0n does not encrypt files, so there is no extension and no ransom note file; identification rests entirely on the extortion side:

  • The organisation appears on n0n's dark web leak site, first anonymised as "Company #N" and then named, with a countdown, one to three days later.
  • The page carries the volume of stolen data and samples. In the maritime batch these are mostly EDI messages, manifests, gate records, terminal configuration and invoices, from tens of megabytes to a few gigabytes.
  • Payment is demanded in Bitcoin to a unique address per victim, with the option of a 10% "entry fee" to open a private negotiation room.

If the contact comes directly by email or messaging, check it against these features and the leak-site page, and be alert to scammers using the n0n name.

Infection vectors

SOCRadar's group profile. n0n logs in with credentials harvested by infostealers, then manipulates data with administrative tools; it has taken Active Directory mappings and legal documents.

Likely entry for the maritime batch. The data sets are small and scoped to single applications, and when SOCRadar checked stealer logs many of the maritime victims had no credential matches. It therefore infers that a platform these organisations share or use to exchange data - a terminal operating system, an EDI integration or a file-transfer product - is the more likely source than 38 separate intrusions. That is inference, not confirmed, and SOCRadar notes no evidence linking n0n to MOVEit (2023) or Cleo (2024).

For port and logistics companies, investigation cannot stop at their own network: ask the vendors of any shared platform whether they are investigating.

Encryption behavior

No public report has observed n0n encrypting files. SOCRadar's ATT&CK mapping lists encryption and recovery-inhibition techniques, but its write-up says the group avoids traditional ransomware deployment and concludes it should be "treated as a data-theft extortion operation with the access to cause damage".

Response therefore centres on scoping the exfiltration, meeting notification duties and removing access - and as long as the intruders' access remains, later damage cannot be ruled out, so it has to be taken back.

Assess before you act

Recoverability assessment

Nothing is encrypted in an n0n incident; what needs recovering is control. We do not pay ransoms and do not negotiate; our work is leak assessment, forensics and hardening.

1) Verify the intrusion. Leak-site claims may be inflated, or the data may have come from a vendor. Use access logs, file-transfer records, EDI gateways and database auditing to check whether the sample files came from your systems and when they were accessed.

2) Scope the exfiltration. Establish what left, how much, when and through which system or account, and whether customer, partner or personal data is involved; that drives regulatory, contractual and customer notification.

3) Take access back. Rotate SFTP, AS2, VAN and vendor support credentials, starting with shared and long-lived ones; check for infostealer infections; enforce MFA on VPN and RDP and review recent remote logins.

4) Coordinate across the supply chain. If the data came from a shared platform, share information with the vendor and with other listed peers rather than investigating in isolation.

We deliver verifiable findings and make no unprovable promises such as "the data has been deleted".

Our response plan

Hit by n0n ransomware? What to do

  1. Verify the claim and preserve evidence

    Capture the leak-site page and samples, and match the sample files to their source systems and access times. At the same time export logs from EDI gateways, file-transfer services, VPN, RDP and identity systems before rotation overwrites them. Do not rush to rebuild or clean servers.

  2. Exfiltration scoping

    Use log and traffic evidence to establish the data types, volume, time window and channel of the exfiltration, and whether your own systems or a shared platform or vendor leaked the data; produce the factual basis for notification.

  3. Revoke access and rotate credentials

    Rotate SFTP, AS2, VAN, vendor support and service accounts; hunt for infostealers; enforce MFA; patch and review internet-facing EDI, file-transfer and terminal-system components; look for unusual access and bulk downloads.

  4. Notification and ongoing monitoring

    Complete regulatory, contractual and customer notification and prepare external messaging; keep watching the leak site and dark web for follow-on publication; close with an incident report and hardening checklist.

Risk warning

What not to do

  • Do not treat this as a routine security event because nothing is encrypted and operations continue - the damage is on the leak side, and delay burns notification deadlines.
  • Do not pay the "entry fee" or the ransom; payment cannot prove deletion, and copies can still be resold or used to extort you again.
  • Do not investigate only your own network; a shared platform or vendor may be the real source.
  • Do not reopen data-exchange channels with vendors before credentials are rotated.
  • Do not respond to direct messages using the n0n name without checking them against the leak-site page.

Emergency response

Data already encrypted? Stop and let an engineer look first

We do not pay ransoms and we do not negotiate with attackers. Engineers run a free assessment first, then propose a recovery plan and a firm quote.

Related industries

Similar families

FAQ

n0n Frequently asked questions

  • Is n0n ransomware? Does it encrypt files?

    n0n is an extortion crew, but no public report has observed it encrypting files. It steals data, lists the victim on its dark web leak site with a countdown, and demands Bitcoin under threat of publication. Response therefore focuses on confirming whether data was really taken, what and from where, and on meeting notification duties.

  • We are a port or logistics company on n0n's list but have found nothing unusual - what now?

    Start with the samples. SOCRadar infers the maritime data may have come from a platform the victims share - a terminal system, an EDI integration or a file-transfer product - rather than from separate intrusions, so finding nothing on your own network does not mean nothing leaked. Do three things in parallel: match the sample files to their source system, ask the shared platform's vendor whether it is investigating, and rotate the SFTP, AS2, VAN and vendor support credentials tied to that platform.

  • Can paying the "entry fee" get the price down?

    We advise against paying anything. n0n's 10% entry fee to open a private negotiation room is itself the first payment, and after paying there is no way to verify the data was deleted - copies can still be resold or used again. Resources are better spent on scoping the leak, notification and taking access back.