MalwareTips

File scan report

Scan another file

Verdict Malicious

Analyzed , 1 month ago

Is SacredStep_BETA_v2.exe safe? No, we rate this exact file malicious.

Unsigned 30-day-old PE with 5 major detections and 4 YARA rules matching offensive tooling.

Strong evidence · Two or more major antivirus engines agree.

Don't run this file

If you already ran it, follow the steps below.

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 you typed passwords on the device after running it, change them from another device you trust.

  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

SacredStep_BETA_v2.exe: Malicious — MalwareTips file scan

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

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

Antivirus results

26 of 70 flagged

  • Flagged 26
  • No detection 44
  • No result 5
FileSacredStep_BETA_v2.exe455.2 kBSHA-256 526b85947cf0…786481
  • Code signing Unsigned
  • Test run Completed
  • First seen 2mo ago
26 of the 70 antivirus engines that checked it flag it, including Microsoft and Symantec (Norton).

Chapter 02

Why we think so

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

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

26 of the 70 antivirus engines that checked it flag the file, including 5 major antivirus engines naming SONBOKLI or Wacatac families. The sample is unsigned, drops executables, and contacts direct IPs while matching multiple YARA rules for Cobalt Strike and ransomware activity.

Where this verdict could be wrong2 caveats
  • contactedHosts.inspected=1 and maliciousHosts.length=0 — no cached malicious host match for the observed IPs.
  • droppedChildren.rollup.malicious=0 across 3 inspected children — no confirmed malicious file it created.

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 · 5 complete · 1 partial. 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
  • 11sandbox rule tags
  • 4spawned processes
  • 3network contacts
  • 9filesystem & 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: Checked whether it was running on a test computer.

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

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

  • Note: Read basic details of the test computer, such as its Windows version.

  • Note: Looked through folders on the test computer (most installers do this).

  • Note: Loaded extra code modules while running.

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 trojans work

A trojan pretends to be something useful or harmless so that you run it. Once open, it does its real job in the background, from stealing data to opening a back door or downloading more malware.

Bottom line:The disguise is the whole trick, so a trustworthy-looking name or icon means nothing.

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

      SacredStep_BETA_v2.exe

      526b85947cf0fba1df3e14ce8a3a7b5195174c291bf4402832066d770d786481

      Uploaded file

  2. Processes

    What ran

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

      SacredStep_BETA_v2.exe

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

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

      run_c44ae31.exe

      "C:\Users\<USER>\AppData\Local\SacredStep\run_c44ae31.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

      run_c44ae31.exe

      C:\Users\<USER>\AppData\Local\SacredStep\run_c44ae31.exe

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

      offsets_cache.json

      C:\Users\<USER>\AppData\Roaming\SacredStep\offsets_cache.json

      Test run
    3. +1 more recorded observation

  4. Network

    Hosts contacted

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

      104.21.32.125

      Contacted during the test run.

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

      172.67.151.247

      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

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

Sources checked

Every check behind this verdict

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

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteRisk signal: 26 of 70 engines flagged it · 5 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteRuntime behaviour was recorded Details for sandbox run
Contacted hostsMalwareTips URL scannerPartial1 of 3 contacted hosts were cross-checked; coverage is incomplete Details for contacted hosts
Signature rulesYARAify community rules + MalwareTips rulesComplete4 community YARA rules (generic only) Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

Engines that flagged it 26

  • Fortinet (major engine)W32/PossibleThreat
  • Microsoft (major engine)Trojan:Win32/Wacatac.B!ml
  • Sophos (major engine)Mal/Generic-S
  • Symantec (major engine)ML.Attribute.HighConfidence
  • TrellixENS (major engine)Artemis!06616776FB47
  • TrendMicro (major engine)Trojan.Win64.SONBOKLI.USBLHM26
  • TrendMicro-HouseCall (major engine)Trojan.Win64.SONBOKLI.USBLHM26
  • Antiy-AVLTrojan/Win32.Agent
18 more in the full engine list

File fingerprint

Last analyzed
Sep 7, 2026, 11:30 PM UTC
SHA-256
526b85947cf0fba1df3e14ce8a3a7b5195174c291bf4402832066d770d786481
SHA-1
9df433a7c21ef802b2ee4d0548ee57075a370475
MD5
06616776fb47f741e48fc0b492e1a2d3

About this file

SacredStep_BETA_v2.exe is a Win32 EXE file of 455.2 kB.

Type and size
Win32 EXE · 455.2 kB
Signer
UnsignedNo code signature.
First seen
Aug 8, 2026On VirusTotal.
Submitted by
397 distinct sources
Packer
None detected
Entropy
7.97 of 8

First scanned

Chapter 05

Questions & answers

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

Is SacredStep_BETA_v2.exe a virus?
Yes. This copy of SacredStep_BETA_v2.exe (SHA-256 526b8594…6481) 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. 26 of the 70 antivirus engines that checked it flag it, some as sonbokli. Antivirus engines classify it as a trojan: malware disguised as something harmless so that you run it. If you've already run it, see the steps below.
What is SacredStep_BETA_v2.exe?
SacredStep_BETA_v2.exe is a Windows program, about 455.2 kB. It carries no version information saying what it is or who made it. VirusTotal first saw it on Aug 8, 2026.
How many antivirus engines detected SacredStep_BETA_v2.exe?
26 of the 70 antivirus engines that checked it flag SacredStep_BETA_v2.exe, including Microsoft and Symantec (Norton). We weigh which engines flagged it and what else the scan found, not just the count. The rating comes from all the evidence together, not from this count alone.
What should I do if I already ran SacredStep_BETA_v2.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) Change your important passwords from another device you trust, starting with email and banking, and turn on two-step verification. 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 SacredStep_BETA_v2.exe?
To remove SacredStep_BETA_v2.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 SacredStep_BETA_v2.exe?
Antivirus engines classify SacredStep_BETA_v2.exe as a trojan: malware disguised as something harmless so that you run it. Engines attribute it to the sonbokli family.
What is the SHA-256 hash of SacredStep_BETA_v2.exe?
The SHA-256 fingerprint of SacredStep_BETA_v2.exe is 526b85947cf0fba1df3e14ce8a3a7b5195174c291bf4402832066d770d786481, and its MD5 is 06616776fb47f741e48fc0b492e1a2d3. 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 SacredStep_BETA_v2.exe?
This report reflects the scan on Sep 7, 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.