Is SacredStep_BETA_v2.exe safe?
Unsigned 30-day-old PE with 5 tier-1 detections and 4 YARA rules matching offensive tooling.
26 of 75 engines flag the file, including 5 tier-1 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.
526b85947cf0fba1df…066d770d786481Recommended next actions
Before running
Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already ran it
Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
26 of 75 engines flag the file, including 5 tier-1 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.
Five independent tier-1 engines converge on malicious labels despite a weak family consensus string. The file is unsigned and exhibits direct-IP C2 traffic plus dropped children, while YARAify reports four community rules tied to known offensive frameworks. Medium prevalence and sandbox execution without contradictory clean signals outweigh the absence of cached malicious hosts.
What We Detected
26 of 75 engines report malicious, 5 of them tier-1. TrendMicro, Microsoft, Sophos, Symantec and Fortinet each contribute a detection. YARAify matches four rules, including cobalt_strike_tmp01925d3f and VECT_Ransomware. The PE is unsigned and writes additional executables to AppData\Local\SacredStep.
Threat Behavior
Sandbox execution shows direct IP contact to 104.21.32.125 and 172.67.151.247 plus the URL offsets.femboythighs.org/offsets.json. Mutex Global\SacredStep_v4_Mutex is created and multiple child processes are spawned. No offensive MITRE techniques were recorded, but ambient discovery and evasion behaviors are present.
What To Do Now
Do not execute the file. Keep endpoint protection enabled and submit the sample to your security vendor for further analysis. Review any systems that already ran the binary for persistence artifacts under AppData\Local\SacredStep.
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 dropped payload.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No malicious child verdict from dropped files
- No cached malicious host match
- 5 tier-1 malicious detections
- Unsigned executable
- YARA matches for Cobalt Strike and ransomware
- Direct-IP network traffic
- Dropped child executables
Block the hash, investigate any endpoints that executed SacredStep_BETA_v2.exe, and retain endpoint protection.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete26 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 3 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete5 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 11MITRE ATT&CK techniques
- 4spawned processes
- 3network contacts
- 9filesystem & mutex artifacts
What this file does
Observed actions and their security significance
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Moderate concern: Checks which security software you have installed.
Note: Listed running processes; both legitimate software and malware may do this.
Note: Collects details about your system.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Threat context
How trojans work
A trojan disguises itself as something useful or harmless to trick you into running it. Once open, it does its real job in the background — anything 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.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
SacredStep_BETA_v2.exe
526b85947cf0fba1df3e14ce8a3a7b5195174c291bf4402832066d770d786481
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\SacredStep_BETA_v2.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\SacredStep\run_c44ae31.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
run_c44ae31.exe
C:\Users\<USER>\AppData\Local\SacredStep\run_c44ae31.exe
04Isolated runtime analysis - Written fileObserved
offsets_cache.json
C:\Users\<USER>\AppData\Roaming\SacredStep\offsets_cache.json
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
104.21.32.125
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
172.67.151.247
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 104.21.32.125
- 172.67.151.247
- https://offsets.femboythighs.org/offsets.json
- C:\Users\<USER>\AppData\Local\SacredStep\run_c44ae31.exe
- C:\Users\<USER>\AppData\Roaming\SacredStep\offsets_cache.json
- C:\Users\<USER>\AppData\Local\SacredStep\run_9c37d8e.exe
- C:\Users\user\AppData\Local\SacredStep
- C:\Users\user\AppData\Local\SacredStep\run_1b7743e7.exe
- Global\SacredStep_v4_Mutex
- \Sessions\1\BaseNamedObjects\Global\SacredStep_v4_Mutex
Files this sample writes at runtime
This file drops 3 children at runtime. None are currently flagged malicious in our cache.
- 953caa3748bd07123f77…ce430cNever scannednever seen before
- 50cfe8aa4e796568f3a1…0e4e62Never scannednever seen before
- 93bbfe1005512b53037c…7f8838Never scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 5rule hits recorded
- 26 / 75engines flagged
- 397sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
4 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceObservedSourceSignature and behavior rulesObserved at - 02
26 of 75 antivirus engines flagged the file, including Antiy-AVL and APEX.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
YARAify matched 4 researcher rules to this file.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: SacredStep_BETA_v2.exe — 526b85947cf0fba1df3e14ce8a3a7b5195174c291bf4402832066d770d786481
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\SacredStep_BETA_v2.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\SacredStep\run_c44ae31.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: run_c44ae31.exe — C:\Users\<USER>\AppData\Local\SacredStep\run_c44ae31.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: offsets_cache.json — C:\Users\<USER>\AppData\Roaming\SacredStep\offsets_cache.json
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 104.21.32.125 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 172.67.151.247 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: generic-trojan
One or more independent reference databases matched this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
- cobalt_strike_tmp01925d3f
- DebuggerCheck__API
- golang_bin_JCorn_CSC846
- VECT_Ransomware
The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence104.21.32.125 · 172.67.151.247
26 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- SacredStep_BETA_v2.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 444.5 KB
- Last analyzed
- Sep 7, 2026, 11:30 PM UTC
526b85947cf0fba1df3e14ce8a3a7b5195174c291bf4402832066d770d786481Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file is dangerous. Treat it as harmful and remove it.
- Recovery step 01
Don't run this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already ran it, disconnect from the internet and start with a full antivirus scan or Microsoft Defender Offline scan. If compromise is suspected or the problem persists, use a reputable second-opinion scanner and follow incident-recovery or clean-reinstall guidance.
- Recovery step 03
If you typed any passwords while it was open, change them from a device you trust.
- Recovery step 04
Get a fresh copy from the developer's official site or an official app store.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is SacredStep_BETA_v2.exe a virus?
What is SacredStep_BETA_v2.exe?
How many antivirus engines detected SacredStep_BETA_v2.exe?
What should I do if I already ran SacredStep_BETA_v2.exe?
How do I remove SacredStep_BETA_v2.exe?
What kind of malware is SacredStep_BETA_v2.exe?
What is the SHA-256 hash of SacredStep_BETA_v2.exe?
How up to date is this analysis of SacredStep_BETA_v2.exe?
Community
Member reviews and reports for this exact file hash.