File scan report

Verdict Suspicious

Analyzed , 1 month ago

Is RebirthPub_SaveEditor (1).exe safe? Treat it as suspicious.

One major antivirus engine flags it as Trojan.Win64.Gen.TL0101HM26ZX while 15 major antivirus engines remain silent.

Read the whole reasonShow less

Why Suspicious? 7 antivirus engines flag it; 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

Treat as untrusted; keep antivirus enabled and avoid running the executable outside a controlled test environment.

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

7 of 70 flagged

  • Flagged 7
  • No detection 63
  • No result 5
FileRebirthPub_SaveEditor (1).exe16.0 MBSHA-256 ed1b9a5baf2f…8576f8
  • Code signing Unsigned
  • Test run Completed
  • First seen 2mo ago
7 of the 70 antivirus engines that checked it flag it, including Malwarebytes and Trend Micro.

Chapter 02

Why we think so

2 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

The file is unsigned and exhibits two offensive MITRE techniques plus direct-IP contact. Only one major antivirus engine contributes a malicious label, and the family consensus is weak. Similar import-table fingerprint matches produced mixed prior verdicts, and the generic PyInstaller YARA rule adds limited weight. These mixed signals place the sample in the suspicious band.

Where this verdict could be wrong1 caveat
  • No dropped file is known to be malicious and 10 files it created all unknown.

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
  • 15sandbox rule tags
  • 3spawned processes
  • 0network contacts
  • 16filesystem & 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: 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: Read basic details of the test computer, such as its Windows version.

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

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: Showed activity a sandbox rule links to file encryption; no ransomware behaviour was confirmed.

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

      RebirthPub_SaveEditor (1).exe

      ed1b9a5baf2fe4568abe3fe890dc8f9a552449c8502eb6d36008f65c398576f8

      Uploaded file
  2. Processes

    What ran

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

      RebirthPub_SaveEditor.exe

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

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

      cmd.exe

      C:\Windows\system32\cmd.exe /c "ver"

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

    Created or changed

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

      _ARC4.pyd

      C:\Users\<USER>\AppData\Local\Temp\_MEI33802\Crypto\Cipher\_ARC4.pyd

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

      _Salsa20.pyd

      C:\Users\<USER>\AppData\Local\Temp\_MEI33802\Crypto\Cipher\_Salsa20.pyd

      Test run
    3. +1 more recorded observation

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

Chapter 04

Technical details

7 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 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: 7 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 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 7

  • TrendMicro-HouseCall (major engine)Trojan.Win64.Gen.TL0101HM26ZX
  • APEXMalicious
  • BkavW32.Malware.8EF23EF3
  • DeepInstinctMALICIOUS
  • Elasticmalicious (moderate confidence)
  • MalwarebytesRiskWare.Agent
  • SentinelOneStatic AI - Suspicious PE

File fingerprint

Last analyzed
Sep 4, 2026, 8:14 PM UTC
SHA-256
ed1b9a5baf2fe4568abe3fe890dc8f9a552449c8502eb6d36008f65c398576f8
SHA-1
250c5b5eb6fb13115368d2d48d05e1b74479ec79
MD5
8e326f44b2ba228c891a8fbca76bcdf4

About this file

RebirthPub_SaveEditor (1).exe is a Win32 EXE file of 16.0 MB.

Type and size
Win32 EXE · 16.0 MB
Signer
UnsignedNo code signature.
First seen
Aug 18, 2026On VirusTotal.
Submitted by
9 distinct sourcesRarely seen: few people have submitted this exact file.
Packer
None detected
Entropy
8.00 of 8

First scanned

Chapter 05

Questions & answers

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

Is RebirthPub_SaveEditor (1).exe safe, or is it malware?
RebirthPub_SaveEditor (1).exe is rated Suspicious: some signs point to a problem, but nothing confirms it is harmful. 7 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 RebirthPub_SaveEditor (1).exe?
RebirthPub_SaveEditor (1).exe is a Windows program, about 16.0 MB. It carries no version information saying what it is or who made it. VirusTotal first saw it on Aug 18, 2026.
How many antivirus engines detected RebirthPub_SaveEditor (1).exe?
7 of the 70 antivirus engines that checked it flag RebirthPub_SaveEditor (1).exe, including Malwarebytes and Trend Micro. We weigh which engines flagged it and what else the scan found, not just the count.
I already downloaded and ran RebirthPub_SaveEditor (1).exe — what should I do?
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 RebirthPub_SaveEditor (1).exe?
The SHA-256 fingerprint of RebirthPub_SaveEditor (1).exe is ed1b9a5baf2fe4568abe3fe890dc8f9a552449c8502eb6d36008f65c398576f8, and its MD5 is 8e326f44b2ba228c891a8fbca76bcdf4. 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 RebirthPub_SaveEditor (1).exe?
This report reflects the scan on Sep 4, 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.