MalwareTips

File scan report

Scan another file

Verdict Malicious

Analyzed , 7 days ago

Is PrestigeLoader(1).exe safe? No, we rate this exact file malicious.

This unsigned Go program behaved like a password stealer in our sandbox, harvesting browser passwords, cookies, cards and wallets while contacting Telegram, and 31 of the 69…

Read the whole reasonShow less

Strong evidence · Two or more major antivirus engines agree.

Don't run this file

Delete this file without running it. If it was run, scan the system, and from a clean device change saved passwords, revoke messaging sessions and secure any crypto wallets.

What to do now4 steps

This file is harmful. Don't run it, and remove it.

If you haven't run it

  1. Don't run this file. Delete it, then empty the Recycle Bin.

If you already ran it

  1. Disconnect the device from the internet, then run a full antivirus scan. Microsoft Defender Offline (Windows Security > Virus & threat protection > Scan options) also finds malware that hides while Windows runs.

  2. If any of your files were locked or renamed, don't pay the ransom: payment rarely brings files back. Restore them from a backup instead.

  3. If the scan keeps finding it, or the device still acts strangely, scan again with a second-opinion scanner from another company; if that doesn't fix it, back up your personal files and reinstall Windows.

If you already ran it, do these in order.

If you opened or installed it

Avoid banking and sign-ins on that device until it is clean. These free MalwareTips guides walk you through it.

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

Why we think so

Share this file report

PrestigeLoader(1).exe: Malicious — MalwareTips file scan

The link always shows the latest result for this exact file (its SHA-256 fingerprint).

Antivirus results

31 of 69 flagged

  • Flagged 31
  • No detection 38
  • No result 6
FilePrestigeLoader(1).exe25.8 MBSHA-256 f1ec519a17f9…6be611
  • Code signing Unsigned
  • Test run Completed
  • First seen 1mo ago
A sandbox test run rated its behaviour as malicious.

Chapter 02

Why we think so

6 points against it and 0 in its favour, checked against the scan evidence.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

31 of the 69 antivirus engines that checked it detect this file, many as a password or spyware trojan. In our sandbox runs it injected into a hidden Chrome instance and wrote files of saved passwords, cookies, credit cards, crypto wallets and Discord tokens. It also listed Wi-Fi profiles and contacted Telegram's API, which matches the Kematian stealer.

Where this verdict could be wrong2 caveats
  • No major antivirus engines agree on a single named family, and many labels are generic machine-learning buckets.
  • The file is not listed in MalwareBazaar and has no malware-specific YARAify rule matches.

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 3 isolated tests; 1 test environment rated what it did as risky.

Test run summary

Capture complete
  • 3isolated sandbox runs
  • 20sandbox rule tags
  • 8spawned processes
  • 7network contacts
  • 18filesystem & mutex artifacts

What the test run showed

What the file did on a test computer

Confirmed in the test run

  • High concern: Injected code into another program on the test computer.

  • High concern: Encrypted files on the test computer, as ransomware does.

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

  • Moderate concern: Hid files or windows on the test computer.

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

  • Note: Deleted files or logs during the test run (installers often clean up after themselves).

  • 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 password-store access, but nothing touched the Windows password store.

  • Not confirmed: A sandbox rule tagged this run as searching for passwords; no password file was read.

  • Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change 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.

Threat context

How password stealers work

A password stealer runs quietly in the background and copies your private data, such as saved passwords, browser cookies, autofill details and crypto wallets, then sends it to criminals. You usually won't notice anything.

Bottom line:Stolen logins are used to break into your accounts or sold in bulk, so change passwords from another device.

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

      PrestigeLoader(1).exe

      f1ec519a17f9686a4162d2b68299cdc7f26b3793db6269c37c969da0c36be611

      Uploaded file

  2. Processes

    What ran

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

      kematian.exe

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

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

      netsh

      netsh wlan show profiles

      Test run
    3. +1 more recorded observation

  3. Files

    Created or changed

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

      passwords.json

      C:\Users\<USER>\AppData\Local\Temp\kematian-2777885511\passwords.json

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

      cookies.json

      C:\Users\<USER>\AppData\Local\Temp\kematian-2777885511\cookies.json

      Test run
    3. +1 more recorded observation

  4. Network

    Hosts contacted

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

      accounts.google.com

      Contacted during the test run.

      Test run
    2. Evidence 7 of 7: Contacted hostWorked out from other results

      api.ipify.org

      Older reputation report (safe), not counted as current evidence.

      Contacted-host cross-check
    3. +1 more recorded observation

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

Chapter 04

Technical details

31 of the 69 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: 31 of 69 engines flagged it · 6 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxes · C2AE, CAPE Sandbox, ZenboxCompleteRisk signal: 3 runs: 1 malicious, 2 without a verdict Details for sandbox run
Contacted hostsMalwareTips URL scannerComplete8 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 31

  • Avast (major engine)Win64:Agent-NA [Pws]
  • AVG (major engine)Win64:Agent-NA [Pws]
  • BitDefender (major engine)QD:Trojan.GenericKDQ.2D31D9E016
  • Emsisoft (major engine)QD:Trojan.GenericKDQ.2D31D9E016 (B)
  • ESET-NOD32 (major engine)WinGo/Spy.Agent.NP trojan
  • Fortinet (major engine)W32/PossibleThreat
  • GData (major engine)Win64.Trojan.Agent.BFV9NX
  • Kaspersky (major engine)UDS:Trojan.Win32.Generic
23 more in the full engine list

File fingerprint

Last analyzed
Oct 19, 2026, 10:38 AM UTC
SHA-256
f1ec519a17f9686a4162d2b68299cdc7f26b3793db6269c37c969da0c36be611
SHA-1
78eeac7ed0a3542169fa1e37f6cac63a4a209097
MD5
f4071a2109f2ccca4b38ef0850a7eea4

About this file

PrestigeLoader(1).exe is a Win32 EXE file of 25.8 MB.

Type and size
Win32 EXE · 25.8 MB
Signer
UnsignedNo code signature.
First seen
Sep 20, 2026On VirusTotal.
Submitted by
6 distinct sourcesRarely seen: few people have submitted this exact file.
Packer
None detected
Entropy
6.04 of 8

First scanned

Chapter 05

Questions & answers

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

Is PrestigeLoader(1).exe a virus?
Yes. This copy of PrestigeLoader(1).exe (SHA-256 f1ec519a…e611) is malicious. Other files with the same name can be different, so check the hash. Don't run it. Delete it, then empty the Recycle Bin. 31 of the 69 antivirus engines that checked it flag it, some as Kematian Stealer. Antivirus engines classify it as a password stealer, built to copy saved passwords, cookies and crypto wallets. If you've already run it, see the steps below.
What is PrestigeLoader(1).exe?
PrestigeLoader(1).exe is a Windows program, about 25.8 MB. It carries no version information saying what it is or who made it. VirusTotal first saw it on Sep 20, 2026.
How many antivirus engines detected PrestigeLoader(1).exe?
31 of the 69 antivirus engines that checked it flag PrestigeLoader(1).exe, including Microsoft and Kaspersky. We weigh which engines flagged it and what else the scan found, not just the count. A sandbox test run also rated its behaviour as malicious.
What should I do if I already ran PrestigeLoader(1).exe?
Act quickly. 1) Disconnect the device from the internet. 2) Run a full scan with your antivirus and let it remove what it finds. 3) If files were locked or renamed, don't pay the ransom; restore them from a backup. 4) If you bank or shop on this device, watch your accounts and tell your bank about payments you don't recognise. 5) If the scan keeps finding it, back up your personal files and reinstall Windows.
How do I remove PrestigeLoader(1).exe?
To remove PrestigeLoader(1).exe: 1) run a full scan with your antivirus and let it remove what it finds. 2) Delete it, then empty the Recycle Bin. 3) Check Settings > Apps, your browser extensions, startup apps (Task Manager > Startup apps) and scheduled tasks for anything you don't recognise. 4) Restart and scan again. If it keeps coming back, scan from Safe Mode with Networking, or back up your files and reinstall Windows.
What kind of malware is PrestigeLoader(1).exe?
Antivirus engines classify PrestigeLoader(1).exe as a password stealer, built to copy saved passwords, cookies and crypto wallets. Engines attribute it to the Kematian Stealer family.
What is the SHA-256 hash of PrestigeLoader(1).exe?
The SHA-256 fingerprint of PrestigeLoader(1).exe is f1ec519a17f9686a4162d2b68299cdc7f26b3793db6269c37c969da0c36be611, and its MD5 is f4071a2109f2ccca4b38ef0850a7eea4. 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 PrestigeLoader(1).exe?
This report reflects the scan on Oct 19, 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.

Related file reports

Recent reports on other files with the same rating.

All file reports
Scan another
Check a different file
URL instead?
Check if a link is safe
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.