File scan report

Verdict Suspicious

Analyzed , 12 days ago

Is FateInjector.exe safe? Treat it as suspicious.

8 of the 70 antivirus engines that checked it flag this Windows program, but nothing confirms it is harmful.

Why Suspicious? 8 antivirus engines flag it and one of our detection rules matched it.

Moderate evidence · More than one sign points to a problem, but nothing confirms it is harmful.

Don't run it until you know where it came from

If it came from a link, an attachment or a stranger, delete it.

What to do now4 steps

Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.

What to do

  1. Don't run it unless you're sure where it came from.

  2. Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.

  3. If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.

If you already ran it

  1. Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.

Not sure what to do?

Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.

Paste this report's link in your topic so helpers can see what was found.

Reads the latest antivirus results for this file's hash. Nothing is uploaded.

Antivirus results

8 of 70 flagged

  • Flagged 8
  • No detection 62
  • No result 5
FileFateInjector.exe3.9 MBSHA-256 77a84c4ed295…8ff70d
  • Code signing Unsigned
  • Test run Completed
  • First seen 5y ago
1 strong detection rule matched this file.

Chapter 02

Why we think so

4 points against it and 5 in its favour, checked against the scan evidence.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

Although only 8 of the 70 antivirus engines that checked it flagged it, the two unwanted program detections from major antivirus engines, unsigned status, and injector behavior warrant avoiding execution outside an isolated research environment.

Where this verdict could be wrong3 caveats
  • The complete reputation check of 25 observed hosts found no malicious or suspicious destinations.
  • Most engines did not flag the file, and the two major detections characterize it as potentially unwanted software rather than agreeing on a malware family.
  • The file is old and widely submitted, which reduces the likelihood that it is a newly emerging threat.

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

6 sources checked · all complete. See every source

Chapter 03

What it did in our test

It ran in our isolated test environment; no test environment rated what it did as risky.

Test run summary

Capture complete
  • 29sandbox rule tags
  • 4spawned processes
  • 3network contacts
  • 26filesystem & mutex artifacts

What the test run showed

What the file did on a test computer

Confirmed in the test run

  • Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).

  • Moderate concern: Ran commands or a script on the test computer.

  • Moderate concern: Used an unusual way to talk to a server.

  • Moderate concern: Checked whether it was running on a test computer.

  • Note: Read the user name of the test computer.

  • Note: Listed the programs running on the test computer.

  • Note: Talked to servers over the internet during the test run.

Sandbox labels we could not confirm (common in safe files too)

  • Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.

  • Not confirmed: A sandbox rule tagged this run as recording keystrokes; no keylogging was confirmed.

  • Not confirmed: A sandbox rule tagged this run as setting up auto-start; no auto-start entry was recorded.

  • Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.

This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.

Recorded behavior

What happened in the test

Grouped by step. The order is not a timeline.

Seen in the test runWorked out from other results
  1. Input file

    The submitted object

    1
    1. Evidence 1 of 7: FileSeen in the test run

      FateInjector.exe

      77a84c4ed29551d8968a9bc5de796d6f8463fa54df8554b3cff91ca83d8ff70d

      Uploaded file
  2. Processes

    What ran

    2
    1. Evidence 2 of 7: ProcessSeen in the test run

      file.exe

      "C:\Users\<USER>\Desktop\file.exe"

      Test run
    2. Evidence 3 of 7: ProcessSeen in the test run

      77a84c4ed29551d8968a9bc5de796d6f8463fa54df8554b3cff91ca83d8ff70d.exe

      ${SamplePath}\77a84c4ed29551d8968a9bc5de796d6f8463fa54df8554b3cff91ca83d8ff70d.exe

      Test run
    3. +1 more recorded observation
  3. Files

    Created or changed

    2
    1. Evidence 4 of 7: Written fileSeen in the test run

      config.txt

      C:\Users\<USER>\Desktop\config.txt

      Test run
    2. Evidence 5 of 7: Written fileSeen in the test run

      config.txt

      ${SamplePath}\config.txt

      Test run
    3. +1 more recorded observation
  4. Network

    Hosts contacted

    2
    1. Evidence 6 of 7: Contacted hostSeen in the test run

      adl.windows.com

      Contacted during the test run.

      Test run
    2. Evidence 7 of 7: Contacted hostSeen in the test run

      sfd-production.azurefd.net

      Contacted during the test run.

      Test run
    3. +1 more recorded observation

7 facts from the test run. See the full activity list.

Chapter 04

Technical details

8 of the 70 antivirus engines that checked it flag it; no publisher signature.

Sources checked

Every check behind this verdict

6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteRisk signal: 8 of 70 engines flagged it · 5 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteCombined summary: clean verdict Details for sandbox run
Contacted hostsMalwareTips URL scannerComplete25 contacted hosts checked Details for contacted hosts
Signature rulesYARAify community rules + MalwareTips rulesCompleteRisk signal: 2 MalwareTips behaviour rules Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

Engines that flagged it 8

  • ESET-NOD32 (major engine)Generik.MSDGRRH potentially unwanted application
  • Sophos (major engine)Generic Reputation PUA (PUA)
  • GoogleDetected
  • GridinsoftTrojan.Win64.CobaltStrike.tr
  • MalwarebytesRiskWare.Injector
  • RisingPUA.Undefined!8.132FE (CLOUD)
  • VaristW64/ABApplication.FJGK-1140
  • YandexTrojan.Igent.b63LeS.1

File fingerprint

Last analyzed
Oct 14, 2026, 12:25 AM UTC
SHA-256
77a84c4ed29551d8968a9bc5de796d6f8463fa54df8554b3cff91ca83d8ff70d
SHA-1
65a9e65bf9b2b683ed93ac9848df8b5c9f3d4297
MD5
9e6de7c7ebd1a00c2f7ddec78ba9403a

About this file

FateInjector.exe is a Win32 EXE file of 3.9 MB.

Type and size
Win32 EXE · 3.9 MB
Signer
UnsignedNo code signature.
First seen
Jan 13, 2021On VirusTotal.
Submitted by
3,723 distinct sources
Packer
None detected
Entropy
6.12 of 8

First scanned

Chapter 05

Questions & answers

Short answers to the 6 questions people ask most about this file.

Is FateInjector.exe safe, or is it malware?
FateInjector.exe is rated Suspicious: some signs point to a problem, but nothing confirms it is harmful. 8 of the 70 antivirus engines that checked it flag it. Don't run it unless you're sure where it came from. If you need the program, download it again from the publisher's own website.
What is FateInjector.exe?
FateInjector.exe is a Windows program, about 3.9 MB. It carries no version information saying what it is or who made it. VirusTotal first saw it on Jan 13, 2021.
How many antivirus engines detected FateInjector.exe?
8 of the 70 antivirus engines that checked it flag FateInjector.exe, including ESET and Malwarebytes. We weigh which engines flagged it and what else the scan found, not just the count.
What should I do if I already ran FateInjector.exe?
No infection is confirmed: the rating is a caution, not a malware finding. 1) Check where it came from. If you can't confirm the source, delete it. 2) Run a full scan with your security software. 3) If the scan finds something, follow its removal steps and change passwords you typed on the device since then.
What is the SHA-256 hash of FateInjector.exe?
The SHA-256 fingerprint of FateInjector.exe is 77a84c4ed29551d8968a9bc5de796d6f8463fa54df8554b3cff91ca83d8ff70d, and its MD5 is 9e6de7c7ebd1a00c2f7ddec78ba9403a. Two files with the same SHA-256 are identical, so use it to check you have exactly this file, not just one with the same name.
How up to date is this analysis of FateInjector.exe?
This report reflects the scan on Oct 14, 2026. A file's fingerprint never changes, but antivirus engines keep learning, so a rating can change later. To get a newer result, scan the file again: we refresh the antivirus results when the saved ones are out of date.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Recent reports on other files with the same rating.

All file reports
This report and its SHA-256 fingerprint are public, so the next person who checks the same file gets an instant answer; documents and images are listed by type instead of their file name. A file we had not seen before is uploaded to VirusTotal, whose security partners and subscribers can download it; MalwareTips deletes its own copy after the scan. If you ran this file and are worried, scan your device with up-to-date security software.