Suspicious
Single tier-2 generic detection plus direct-IP contact without domains creates moderate suspicion for this unsigned rare executable.
b3b424ab934451178e…5be8095e2aThe reasoning behind this verdict
The MT AI Engine weighs every signal from this scan — antivirus detections, sandbox behaviour, code signing, prevalence and historical matches — to reach a single, evidence-based verdict.
Our analysis weighs the single tehtris Generic.Malware flag against the complete absence of tier-1 detections and the clean sandbox outcome. The direct-IP C2 heuristic is a legitimate red flag because benign software almost always resolves domains, yet it remains a single medium-severity rule without supporting malicious behaviour or dropped payloads. Unsigned status and rare_old prevalence add uncertainty but do not rise to malicious on their own. Similar-hash RAG returned no prior verdicts, leaving the mixed signals unresolved.
Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.
engines.topDetections[0]: tehtris tier2 Generic.Malware
triggeredHeuristics[0]: MalwareTips.Synth.DirectIpC2 fired true with evidence 23.216.81.152 · 52.154.209.174
behaviour.contactedIps: 2 external IPs and 0 domains
signing.signed: false; prevalence.classification: rare_old
- Zero tier-1 malicious detections
- Clean sandbox verdicts
- No malicious dropped children
- No external intelligence hits
- Direct external IP contact without domains
- Single AV detection (tehtris Generic.Malware)
- Unsigned executable
- Rare_old prevalence (3 submitters)
Exercise caution and avoid execution on production systems; re-evaluate with additional context or updated scans.
What this file does
What it attempted when executed in an isolated sandbox
High concern: Talks to a remote server to take commands or send out your data.
High concern: Hijacks how Windows loads programs so it runs automatically.
Moderate concern: Obfuscates or packs its code to avoid detection.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Checks whether it's being watched in a sandbox before acting.
Moderate concern: Checks which security software you have installed.
Note: Collects details about your system.
Translated from the file's technical behaviour during analysis. It never ran on your device.
What to do now
We couldn't fully clear this file. Treat it with caution.
Don't run it unless you're certain it came from a source you trust.
Check where you got it — an email attachment or a random download link is a red flag.
If you're unsure, delete it. You can always re-download a clean copy from the official source.
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 192.168.0.17
- 23.216.81.152
- 52.154.209.174
- C:\Users\<USER>\Desktop\log.txt
- C:\Users\<USER>\Desktop\config.cfg
- ./log.txt
- ./config.cfg
- C:\Users\<USER>\Downloads\log.txt
Files this sample writes at runtime
This file drops 3 children at runtime. None are currently flagged malicious in our cache.
- e3b0c44298fc1c149afb…52b855Never scannednever seen before
- 802449f39a2b6f572004…8c195aNever scannednever seen before
- dfd4e8d7e69a3bbbd651…ca6bdbNever scannednever seen before
YARA & heuristic rule matches
One or more medium-severity heuristic rules matched. Not definitive, but the patterns match known malware behaviour.
Sample contacted 2 external IP address(es) and zero domains. Benign software virtually always uses DNS; no-DNS direct-IP C2 is a strong malware indicator because it bypasses reputation systems and dodges domain-based blocklists.
Evidence23.216.81.152 · 52.154.209.174
1 detection across 79 engines
Section entropy & packers
Section-level entropy and packer detection from the PE header. Nothing suspicious here — entropy is within the normal range for unpacked code.
How widely this file has been seen
Rarely uploaded, but has been around for a while. Often niche legitimate software or old internal tooling; not a strong malware signal on its own.
Forensic fingerprint
- File name
- Tracking.exe
- Size
- 11.03 MB
- MIME type
- (unknown)
- Detected type
- Win32 EXE
- SHA-256
- b3b424ab934451178eb5343cb4a9131a848f71badca5d8a1b5579d5be8095e2a
- MD5
- d468098873adb090ea6252b3aabd9456
- SHA-1
- 415fa88e99366972fe44d773b820a1e1eb61dcdb
- PE imphash
- 91802a615b3a5c4bcc05bc5f66a5b219
- First seen (VT)
- 8/6/2024, 5:55:09 AM
- Last analysis (VT)
- 8/6/2024, 5:56:02 AM
- First scan (MalwareTips)
- 6/6/2026, 10:04:52 PM
- Last scan (MalwareTips)
- 6/6/2026, 10:04:52 PM
Safety FAQ
Common questions about Tracking.exe, answered from the scan data above.
- Tracking.exe is suspicious — treat it as unsafe until you're sure. 1 of 79 antivirus engines flag it, which isn't a strong consensus but is enough to be cautious. Don't run it unless you fully trust where it came from, and prefer downloading the software fresh from its official site.
- Tracking.exe is a Windows executable program, about 11 MB. We identify a file by its cryptographic hash rather than its name, because the same filename can be reused by completely different files — the hash below is the reliable fingerprint.
- 1 of 79 antivirus engines flagged Tracking.exe, 1 of them as outright malicious. A small number of detections can include false positives, so we weigh which engines flagged it and what else the file does, not just the raw count.
- Act quickly. 1) Disconnect the device from the internet to stop the malware communicating or spreading. 2) Run a full scan with reputable anti-malware software (such as Malwarebytes) and quarantine everything it finds. 3) Change your important passwords from a DIFFERENT, clean device — many threats log keystrokes or steal saved credentials. 4) If you bank or shop on this device, watch closely for fraud and alert your bank. 5) For a confirmed infection, the most reliable fix is to back up your personal files and reinstall the operating system for a clean start.
- To remove Tracking.exe: 1) restart into Safe Mode (Safe Mode with Networking if you need to download a tool) so the malware doesn't auto-start. 2) Run a full scan with reputable anti-malware software and let it quarantine or delete the detections. 3) Delete the original Tracking.exe file and empty the Recycle Bin/Trash. 4) Check your browser extensions, startup items, and scheduled tasks for anything unfamiliar. 5) Reboot and scan again to confirm it's gone. If detections keep coming back, a clean operating-system reinstall is the most dependable cure.
- The SHA-256 hash of Tracking.exe is b3b424ab934451178eb5343cb4a9131a848f71badca5d8a1b5579d5be8095e2a, and its MD5 is d468098873adb090ea6252b3aabd9456. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
- This report reflects the scan run on June 6, 2026. Because a file's hash never changes, the identity of Tracking.exe is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.
Reviews & malware reports(0)
Tell the community what you saw. Tag the sample — Trojan, Adware, False Positive — and share what the file did on your system. Your report helps confirm or dispute the AV verdict.