MalwareTips

File scan report

Scan another file

Verdict Suspicious

Analyzed , 10 days ago

Is sora_1st.exe safe? Treat it as suspicious.

Four of the 68 antivirus engines that checked it raised generic alerts, but no major detector, named malware family, or concrete runtime artefact corroborates those findings.

Read the whole reasonShow less

Why Suspicious? 4 antivirus engines flag it, but no major engine agrees; nothing else confirms it.

Limited evidence · One sign points to a problem; nothing else confirms it.

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.

Why we think so

Share this file report

sora_1st.exe: Suspicious — 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

4 of 68 flagged

  • Flagged 4
  • No detection 64
  • No result 7
Filesora_1st.exe451.1 kBSHA-256 2e4fbe9e5f1b…7f3d28
  • Code signing Unsigned
  • Test run Completed
  • First seen 1mo ago
4 of the 68 antivirus engines that checked it flag it, including Deep Instinct and APEX.

Chapter 02

Why we think so

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

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

Four of the 68 antivirus engines that checked it flagged this unsigned and rarely submitted executable, although three detections came from less reliable engines and the remaining alert was generic. The sandbox runs did not reproduce harmful activity, but the absence of a verified publisher and established reputation means the file should not yet be trusted.

Where this verdict could be wrong3 caveats
  • The combined sandbox summary returned a clean assessment and recorded no named injection target, persistence indicator, dropped file, or sample-originated network contact.
  • None of the major antivirus engines flagged the file, and all four detection labels are generic rather than identifying a malware family.
  • The executable is not packed and its code section does not show unusually high entropy.

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 not needed or not applicable. 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
  • 10sandbox rule tags
  • 2spawned processes
  • 0network contacts
  • 0filesystem & 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.

  • 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.

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 contacting a server, but no contacted host was recorded.

  • 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.

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 3: FileSeen in the test run

      sora_1st.exe

      2e4fbe9e5f1b016f6ebc1a13924ee1350e29e15141f2b0710d020507887f3d28

      Uploaded file

  2. Processes

    What ran

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

      sora_1st.exe

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

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

      sora_1st.exe

      "C:\Users\user\Desktop\sora_1st.exe"

      Test run
    3. +1 more recorded observation

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

Chapter 04

Technical details

4 of the 68 antivirus engines that checked it flag it; no publisher signature.

Sources checked

Every check behind this verdict

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

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteRisk signal: 4 of 68 engines flagged it · 7 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteCombined summary: clean verdict Details for sandbox run
Contacted hostsMalwareTips URL scannerNot neededThe sandbox recorded no contacted hosts to checkNo date recorded
Signature rulesYARAify community rules + MalwareTips rulesComplete1 MalwareTips behaviour rule Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

Engines that flagged it 4

  • APEXMalicious
  • BkavW32.Malware.5CB1D1B0
  • DeepInstinctMALICIOUS
  • MaxSecureTrojan.Malware.300983.susgen

File fingerprint

Last analyzed
Oct 15, 2026, 9:30 PM UTC
SHA-256
2e4fbe9e5f1b016f6ebc1a13924ee1350e29e15141f2b0710d020507887f3d28
SHA-1
171ebdbfe068f72250d3b19f7e888d4865dcf8d9
MD5
26b0d742d45d59a821a95b2377331807

About this file

sora_1st.exe is a Win32 EXE file of 451.1 kB.

Type and size
Win32 EXE · 451.1 kB
Signer
UnsignedNo code signature.
First seen
Sep 2, 2026On VirusTotal.
Submitted by
3 distinct sourcesRarely seen: few people have submitted this exact file.
Packer
None detected
Entropy
6.90 of 8

First scanned Updated

Verdict history

  1. Not fully confirmed
  2. Suspiciousafter the analysis was completed

Ratings change when antivirus engines, our checks or MalwareTips staff learn more about a file.

Chapter 05

Questions & answers

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

Is sora_1st.exe safe, or is it malware?
sora_1st.exe is rated Suspicious: some signs point to a problem, but nothing confirms it is harmful. 4 of the 68 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 sora_1st.exe?
sora_1st.exe is a Windows program, about 451.1 kB. It carries no version information saying what it is or who made it. VirusTotal first saw it on Sep 2, 2026.
How many antivirus engines detected sora_1st.exe?
4 of the 68 antivirus engines that checked it flag sora_1st.exe, including Deep Instinct and APEX. We weigh which engines flagged it and what else the scan found, not just the count.
What should I do if I already ran sora_1st.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 sora_1st.exe?
The SHA-256 fingerprint of sora_1st.exe is 2e4fbe9e5f1b016f6ebc1a13924ee1350e29e15141f2b0710d020507887f3d28, and its MD5 is 26b0d742d45d59a821a95b2377331807. 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 sora_1st.exe?
This report reflects the scan on Oct 15, 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

Other files people checked with the same name, and recent reports with the same rating. A matching name does not make two files the same: only the SHA-256 fingerprint identifies a file.

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.