GridinSoft Threat Intelligence
speedtest.exe file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2024-05-11 23:01:04 (2 years ago); latest analysis 2026-01-06 23:00:46 (4 months ago).
Company metadata: Ookla. Product metadata: Speedtest-CLI.
Signed by admin@officertool.org. The signature is not reported as trusted and valid, which can indicate tampering, repackaging, or copied publisher data.
ThreatInfo has seen this file in user or system paths listed below. Unexpected locations increase the need for local verification.
Recommended action
What to do next
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
speedtest.exe is a Windows file recorded in the ThreatInfo database. It is associated with Speedtest-CLI. The reported company name is Ookla. The current detection status is Undefined, based on the latest analysis from 2026-01-06 23:00:46 (4 months ago).
ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.
File Details
| Product Name: | Speedtest-CLI |
| Company Name: | Ookla |
| MD5: | e835c0a80c1f62a1969a955f936be560 |
| Size: | 864 KB |
| First Published: | 2024-05-11 23:01:04 (2 years ago) |
| Latest Published: | 2026-01-06 23:00:46 (4 months ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2026-01-06 23:00:46 (4 months ago) |
Overview
| Signed By: | admin@officertool.org |
| Status: | Invalid (digital signature could be stolen or file could be patched) |
The signature on speedtest.exe is not reported as trusted and valid. Invalid or suspicious signature data can indicate tampering, repackaging, or an unrelated file using copied publisher information.
Common Places:
| %profile%\downloads\morphs_installs_april_2024-teamos\morphs_installs_april_2024-teamos\installs\ntlite\officetoolportable.exe\office(r)tool 12.00 portable\data |
| %sysdrive%\برامج مضغوطه 2025\farescd.com-officertool-v16.2.0.zip\farescd.com-officertool-v16.2.0\data |
| %sysdrive%\isos_weitere\office_2021_retail\click_2run\officer_tools\officertool.v12.rev.f.rar\data |
ThreatInfo has observed speedtest.exe in the locations listed above. Files found in temporary folders, user profile folders, startup locations, or unusual application directories should be reviewed more carefully than files installed under a known program directory.
Geographic signal
Observed country distribution
ThreatInfo has seen speedtest.exe across 3 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Singapore with 33.3% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for speedtest.exe is Windows 10 with 100.0% of observed hits. If your system differs from the common profile, check whether the file was introduced by a specific installer, archive, or removable device.
Analysis
speedtest.exe is identified as pe for 64-bit systems. The subsystem is Windows CUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
d41d8cd98f00b204e9800998ecf8427e
fbdc59ff3159c3d072c838f2416a7293
fb1c904cacd86c1de186b5b07a951d5f
PE section names and hashes can reveal packing, injected resources, or unusual build artifacts. Sections with uncommon names, very large raw data, or hashes that differ from a trusted copy deserve additional review.
Report conclusion
This file is still under review
ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.