Case study
TellYouThePass hits a logistics company's ERP server
An unpatched internet-facing ERP component was hit by an automated TellYouThePass deployment, cutting off order and waybill data. Recovery combined database backups with remnant files, followed by a fleet-wide exposure sweep.
- Industry
- Logistics and Supply Chain Ransomware Response
- Family
- TellYouThePass
- Scenario
- ERP Encrypted
- Handled
- 2026-04
This case study is composed from typical scenarios to illustrate our approach and the recovery paths involved. It does not describe a specific customer incident; real cases involving customer data are published only with authorization.
第 2 个工作日
ERP back in service
约 98%
Order and waybill data recovered
2 台,1 台及时阻断
Additional exposed assets found
0
Ransom paid
Incident background
The client is a regional logistics company whose ERP system offers order placement and carrier lookup to external customers, with the application server and database on one Linux host and a separate Windows host holding scanned waybills and electronic receipts.
Because the business required customers to have round-the-clock access, the ERP web port was exposed directly to the internet, the middleware and business components had received only one minor update since go-live, and the operations team had no patch-tracking process for that system.
One weekday afternoon, customer service reported that clients could not place orders. Operations found the web service returning errors, application directories and database files carrying a uniform appended suffix, and ransom notes in both HTML and text form — the page displaying bilingual Chinese and English text with contact details. The scanned-document directory on the Windows host was encrypted as well.
Worth noting: this kind of incident is usually not targeted. The actor scans the internet at scale, deploys the encryptor automatically on any instance matching a known vulnerability, and the gap between intrusion and encryption is often very short. Company size and industry are not selection criteria.
What we did
With automated mass deployment the key insight is that the affected asset is rarely the only one, so the sweep covered every internet-exposed asset from the start.
- Containment and sweep. Public access to the ERP was cut immediately and all outbound port mappings inventoried. Two test hosts were found running the same component version and equally exposed; one already had suspicious processes but had not yet been encrypted, and was isolated in time.
- Evidence. Web access, application and system logs were preserved, and an anomalous request sequence followed by script files written to disk was located just before encryption — the timeline evidence for the entry point.
- Family confirmation. The note format and encryption characteristics identified the Linux build of TellYouThePass, with no usable public decryptor.
- Recovery. A nightly logical backup of the ERP database was written to a separate internal backup host that was not exposed and not affected, and became the primary source. Orders and waybills created during that day were reconstructed from application logs, notification records sent to customers and carriers, and unencrypted temporary exports. Most scanned documents on the Windows host were recovered from unencrypted remnants and historical archives.
- Hardening. Components were upgraded to a supported version, the web port moved behind a reverse proxy with source restrictions, and a patch-tracking inventory established for internet-facing assets.
Recovery result
The ERP was serving customers again on the second business day, with order and waybill data restored to the previous night's backup point and that day's transactions rebuilt by cross-referencing multiple sources; customer service and dispatch completed reconciliation within one business day. Most historical scanned documents and receipts were recovered, and the small number of recent files missing were re-captured.
Attribution pointed unambiguously at the internet-facing application component: logs showed automated probing from many different addresses, followed by script writes, retrieval of the encryptor and execution — all within a very short span, with no meaningful lateral movement or data staging. That profile matches mass deployment rather than a targeted intrusion, and the same scripts found on the not-yet-encrypted test host confirmed it.
The main lesson here is not about recovery technique but about asset management: anything exposed to the internet needs an inventory entry, a named patch owner and version tracking. After remediation the client routed all external services through a single gateway with a unified patch process, stopped exposing test environments publicly, and re-reviewed the isolation of the backup host.
This is an illustrative case compiled from typical scenarios and anonymized; it does not refer to any specific client.
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 content
ERP System Encrypted by Ransomware
An encrypted ERP is not a single broken database: the application tier, database, attachments and interfaces fail together, halting finance, procurement, production and inventory. This page covers the vulnerability entry points seen in Chinese ERP deployments, the order in which the four tiers are recovered, and how account sets are reconciled at sign-off.
Logistics and Supply Chain Ransomware Response
Logistics is acutely time-sensitive: when TMS, WMS, dispatch and sorting systems stop, goods pile up in warehouses and on routes immediately, and the effect propagates up and down the supply chain. This page covers the sector's threat profile, a recovery order built around goods movement, and hardening for EDI-interconnected environments.
- No public decryptor
TellYouThePass
TellYouThePass is the archetypal vulnerability-driven ransomware family in China, mass-deployed against internet-facing ERP, OA, finance and middleware systems. It appends .locked and hits both Windows and Linux servers. No public decryptor exists.