While the application was first developed for GM OBD-I ECUs, it uses a very flexible way of parsing ECU data stream that has proven useful to a lot of other car enthusiasts such as owners of BMW, Ford, DSM (Mitsubishi), Porsche, etc. The application also includes a complete tuning interface as well as data log file viewers which are in the form of time series, maps and scatter plots.
Learn More Download NowThe application has three big components: dashboards where data coming from the ECU can be displayed in various formats, a tuning section and data log file viewers.
Customize the dashboards with any indicators you want to see
Android sensors on your device are used to display useful GPS geolocation data (including speed) as well as triple axis accelerometer data (including g-force)
Display the app in your windshield to see it at a glance
Look at the data you just data logged on your phone or tablet using the build-in time series, maps or scatter plot log viewers
Tune on the fly using supported real-time tuning hardware or edit a binary file to program a chip later
We try to answer email from our customers as fast as we can, more often than not, we will answer within 24 hours
The application uses ADX and XDF files which are files from TunerPro (Windows software). These files can be found on various sites such as TunerPro Web site itself, GearHead EFI forums as well as your cars enthusiasts forums related to your specific vehicle.
Here is the easy steps that you can follow that will get you going
Find the ADX file for your vehicle. This is often the hardest part. Once your've found it, the rest is easy!
Install the ALDLdroid application from Google Play
Use the Import Data stream feature of the application to import your ADX file.
Connect the ALDL cable to your vehicle diagnostic port. Hit the Connect to ECU menu in the application and watch the data come in!
The application supports various hardware that can be wired or connected wirelessly to your Android device. Here is what is currently supported:
Wired connection (USB) and wireless (Bluetooth) are both supported by the app. For Bluetooth, we suggest the Red Devil River adapters (or the 1320 electronics if you can find one used) and for USB, any FTDI (USB chip) based cable will do. :obd2allinone should have what you need.
It is possible to program chip for your ECU using the Moates BURN1 (discontinued), BURN2 as well as AutoProm.
For real-time tuning, the application currently support the Moates hardware as well. That is the Ostrich as well as the AutoProm.
If you ECU is equipped with an NVRAM module for real-time tuning, that is also supported for some ECU. Mainly Australian ECUs at this point and more can be added as required.
Some of the features described above can be seen on the screenshots below.
We love to see what our customers do with our application so here a video of Boosted & Built Garage and his pretty awesome setup.
Recent variants (v3.2+) include:
Once the user extracts and executes the file:
In the rapidly evolving landscape of malware distribution, threat actors continuously seek new ways to bypass traditional security controls. One such emerging threat is tdork.zip — a malicious archive file that has gained notoriety for delivering a sophisticated information stealer (infostealer) primarily through phishing campaigns and malvertising. Unlike conventional malware that relies on executable files, tdork.zip leverages social engineering and the inherent trust in compressed folders to infiltrate systems, exfiltrate sensitive data, and establish persistent backdoor access.
This article provides a comprehensive technical analysis of tdork.zip, including its infection chain, payload characteristics, evasion techniques, indicators of compromise (IoCs), and defensive countermeasures.
rule tdork_loader_2026
meta:
description = "Detects tdork.zip loader script"
date = "2026-04-20"
strings:
$s1 = "tdork" nocase wide ascii
$s2 = "Invoke-WebRequest -Uri" ascii
$s3 = "WScript.Shell" ascii
$s4 = "RegAsm.exe" ascii
condition:
uint16(0) == 0x5A4D or (filesize < 500KB and 2 of ($s*) )
"tdork.zip" does not appear to be a widely recognized software package, tool, or official dataset in public documentation or security repositories as of April 2026. The name suggests it may be a private or niche compressed archive related to Google Dorking tdork.zip
, which is a technique used in cybersecurity to find vulnerable systems using advanced search engine operators. Alibaba Cloud
If this is a specific file you have encountered, here is a general framework for reviewing a technical tool or archive of this nature: Review Framework for Technical Archives Source and Trust : Since this is a
file, the most critical factor is where it was obtained. Files from unverified sources (e.g., forums, messaging groups) often contain malware or scripts that could compromise your system. Functionality
: Tools related to "dorking" typically automate the process of querying search engines like Google, Shodan, or Bing to identify exposed directories, login panels, or specific software versions. Efficiency Recent variants (v3
: A "proper" review would measure how quickly the tool processes queries and whether it effectively bypasses rate-limiting or CAPTCHA triggers, which are common obstacles for automated dork scanners. Output Quality
: The value of such a tool lies in its ability to filter results and provide actionable data (e.g., specific URLs or metadata) rather than just raw search links. Safety Recommendation
If you are planning to test this file, it is highly recommended to do so in a sandboxed environment
(such as a Virtual Machine) to prevent any potential malicious code from affecting your primary device. Could you provide more context on where you found or what its intended purpose is? Knowing the "tdork
where it was hosted would help in providing a more specific review. dievus/msdorkdump: Google Dork File Finder - GitHub
MSDorkDump is a Google Dork File Finder that queries a specified domain name and variety of file extensions (pdf, doc, docx, etc), What is Dork? - Alibaba Cloud Community
tdork.zip is not a single piece of malware but a delivery vehicle — a password-protected ZIP archive that contains a malicious implant. The name "tdork" is believed to be an internal moniker used by threat actors (possibly derived from "Tor Dork" or a random generator). The .zip extension is chosen deliberately because:
The malware inside is typically a variant of the RedLine Stealer, Vidar, or a custom .NET-based infostealer, depending on the campaign. Recent samples (2025–2026) show a trend toward Rust-based loaders to hinder reverse engineering.
Subscribe to our email newsletter for useful tips and resources.
Copyright 2026 ALDLdroid. All Rights Reserved.