Threat LensFile scan report

Is WhatsMyComputerDoing_E.exe safe?

Verdict
Safe

Only APEX flagged the signed executable among 76 engines, while all tier-1 engines remained silent and no malware family or harmful child was confirmed.

Only 1 of 76 engines flagged this file, and that detection came from low-trust APEX with no family identification. The valid signature, lack of packing, and absence of confirmed harmful children favor a false alarm, although the sandbox’s process-injection mapping warrants retaining protection and using a trusted download source.

Run with normal care

Obtain the executable from the developer's official channel and verify its signature before running it. Keep antivirus and endpoint protection enabled because the sandbox recorded process-injection and persistence-related mappings.

Read the full analysis
Saved file evidenceAntivirus consensus
1of 76 flagged
Flagged 1No detection 75
Digital specimenWhatsMyComputerDoing_E.exe1d61472bda04b7c935…1885b6ae788047
Size1.6 MB
Code signingIT-Services Thomas Holz (Thomas Holz)
SandboxRuntime complete
First seen6y ago
Evidence3 priority signals
The file has a valid code signature from IT-Services Thomas Holz (Thomas Holz).

Recommended next actions

01

Before running

Run it only when it came from the developer's official site or another source you independently trust.

02

If you already ran it

Keep normal device protection enabled and stop if the file behaves unexpectedly.

Chapter 02

Intelligence

The saved assessment, checked against the scan evidence and recorded coverage.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.

78%Confidence
High
Analyst conclusion

Only 1 of 76 engines flagged this file, and that detection came from low-trust APEX with no family identification. The valid signature, lack of packing, and absence of confirmed harmful children favor a false alarm, although the sandbox’s process-injection mapping warrants retaining protection and using a trusted download source.

Where this verdict could be wrong4 caveats
  • The completed sandbox mapped activity to T1055 process injection and four other offensive techniques, which is more concerning than ordinary installer behavior alone.
  • The signature is verified, but signing.signerStats.found=false and signing.trustedPublisher.matched=false, so no established publisher history independently validates it.
  • The host cross-check inspected 4 hosts, but the runtime listed additional IP contacts; therefore, complete host-reputation coverage is not available.
  • The two imphash matches previously received suspicious decisions, although their different signers make those matches weak.

These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.

Recommended action

Obtain the executable from the developer's official channel and verify its signature before running it. Keep antivirus and endpoint protection enabled because the sandbox recorded process-injection and persistence-related mappings.

Scan transparency

Coverage & freshness

4 of 5 complete

Complete means the check returned a usable result. It does not mean the file is safe.

  • Antivirus

    Complete

    1 of 76 engines flagged the file.

  • Sandbox

    Complete

    1 isolated runtime environment contributed observations.

  • Network

    Partial

    4 of 21 contacted hosts were cross-checked; coverage is incomplete.

  • YARA

    Complete

    1 signature or behavior rule matched.

  • External intel

    Complete

    3 of 3 independent reference sources completed.

Chapter 03

Behavior

Plain-English impact first, then the observed runtime evidence.

Runtime flight recorder

Capture complete
  • 1isolated sandbox run
  • 26MITRE ATT&CK techniques
  • 15spawned processes
  • 21network contacts
  • 35filesystem & mutex artifacts
Chapter 04

Detection & Forensics

Consensus, attribution, signatures, code structure, prevalence, and identity.

Chapter 05

Safety & FAQ

Complete recovery guidance and answers for the next decision.

What to do now

This file appears low risk based on the evidence available now.

  1. Recovery step 01

    Run it only when it came from the developer's official site or another source you independently trust.

  2. Recovery step 02

    A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.

  3. Recovery step 03

    Keep your antivirus and Windows updates switched on so you stay protected.

Safety FAQ

Direct answers grounded in the saved verdict and evidence in this report.

7 evidence-based answers
Is WhatsMyComputerDoing_E.exe safe?
Evidence-based answer
WhatsMyComputerDoing_E.exe appears safe. 1 of 76 antivirus engines flagged it; the 1 detection were treated as non-decisive after the wider evidence was weighed. It carries a verified digital signature from IT-Services Thomas Holz (Thomas Holz). Run it only when it came from the developer's official site or another source you independently trust.
What is WhatsMyComputerDoing_E.exe?
Evidence-based answer
WhatsMyComputerDoing_E.exe is a Windows executable program, about 1.6 MB. Our analysis did not identify a verdict-driving threat signal. It carries a verified digital signature from IT-Services Thomas Holz (Thomas Holz). A file's name can be reused by different files, so we identify it by its cryptographic hash (below).
How many antivirus engines detected WhatsMyComputerDoing_E.exe?
Evidence-based answer
1 of 76 antivirus engines flagged WhatsMyComputerDoing_E.exe, 1 of them as outright malicious. The raw count alone does not establish safety or danger; we also weigh which engines flagged it and corroborating behavior, identity, reputation, and rule evidence.
Is WhatsMyComputerDoing_E.exe digitally signed?
Evidence-based answer
Yes — WhatsMyComputerDoing_E.exe carries a valid digital signature from IT-Services Thomas Holz (Thomas Holz), which confirms the file hasn't been tampered with since that publisher signed it. A valid signature is a positive signal, but note that malware is occasionally signed with stolen or abused certificates, so it isn't proof of safety on its own.
What is the SHA-256 hash of WhatsMyComputerDoing_E.exe?
Evidence-based answer
The SHA-256 hash of WhatsMyComputerDoing_E.exe is 1d61472bda04b7c935cbf842efc18e6cac99aad767d1ebda411885b6ae788047, and its MD5 is 92f29bed5384800c8248ff423a73c10d. 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.
Is it safe to run WhatsMyComputerDoing_E.exe?
Evidence-based answer
Based on the recorded evidence, WhatsMyComputerDoing_E.exe has a low observed risk and is properly signed. The important caveat is source: make sure you downloaded it from the official website or a trusted store, because attackers sometimes distribute malware-laced copies under a legitimate file's name. If your own antivirus flags it, verify the source and the exact hash before overriding the warning.
How up to date is this analysis of WhatsMyComputerDoing_E.exe?
Evidence-based answer
This report reflects the scan run on October 6, 2026. Because a file's hash never changes, the identity of WhatsMyComputerDoing_E.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.
Chapter 06

Community

Member reviews and reports for this exact file hash.

The raw file is processed temporarily and is not retained after processing. Its hash and report are public and permanent, so the next person who checks the same file gets an instant answer. Unknown files may be submitted to VirusTotal for analysis. If you ran this file on your computer and are worried, scan your system with an up-to-date antivirus and change critical passwords from a different device.