Is RebirthPub_SaveEditor (1).exe safe?
Unsigned PyInstaller executable showing process-injection and LSASS-access behaviour with a single tier-1 detection.
One tier-1 engine flags it as Trojan.Win64.Gen.TL0101HM26ZX while 15 tier-1 engines remain silent. Sandbox evidence shows T1055 process injection and LSASS access, yet no malicious children or strong family consensus exist.
ed1b9a5baf2fe4568a…08f65c398576f8Recommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
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.
One tier-1 engine flags it as Trojan.Win64.Gen.TL0101HM26ZX while 15 tier-1 engines remain silent. Sandbox evidence shows T1055 process injection and LSASS access, yet no malicious children or strong family consensus exist.
The file is unsigned and exhibits two offensive MITRE techniques (T1055, T1486) plus direct-IP contact. Only one tier-1 engine contributes a malicious label, and the family consensus is weak. Similar imphash matches produced mixed prior verdicts, and the generic PyInstaller YARA rule adds limited weight. These mixed signals place the sample in the suspicious band.
What We Detected
7 of 75 engines flagged the sample; TrendMicro-HouseCall is the sole tier-1 detection, naming Trojan.Win64.Gen.TL0101HM26ZX. The binary is an unsigned 64-bit PE compiled with PyInstaller and shows high-entropy sections but no known packer signature.
Threat Behavior
Sandbox execution recorded T1055 process injection, LSASS memory access (T1003.001), and direct-IP traffic to 162.159.36.2. Ten dropped children were inspected; none carried malicious verdicts. No persistence mechanisms or registry modifications were observed.
What To Do Now
Do not execute the file on production systems. If the file is required, run it only in an isolated virtual machine with current endpoint protection enabled and monitor for unexpected outbound connections.
Where this verdict could be wrong2 caveats
- engines.tier1Malicious=1 and onlyLowTrustFlagging=false, but tier1FamilyConsensus.strong=false and 15 tier-1 engines reported clean.
- droppedChildren.hasMaliciousChild=false and 10 dropped children 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.
- 15 tier-1 engines reported clean
- No malicious dropped children
- Medium prevalence with 9 submitters
- Unsigned executable
- Process-injection and LSASS-access observed
- Single tier-1 malicious detection
Treat as untrusted; keep antivirus enabled and avoid running the executable outside a controlled test environment.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete7 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete3 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
- 15MITRE ATT&CK techniques
- 11spawned processes
- 1network contacts
- 16filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Encrypted files or data, behaviour commonly associated with ransomware.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
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.
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
RebirthPub_SaveEditor (1).exe
ed1b9a5baf2fe4568abe3fe890dc8f9a552449c8502eb6d36008f65c398576f8
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\RebirthPub_SaveEditor.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\cmd.exe /c "ver"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
_ARC4.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI33802\Crypto\Cipher\_ARC4.pyd
04Isolated runtime analysis - Written fileObserved
_Salsa20.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI33802\Crypto\Cipher\_Salsa20.pyd
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
6 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.
- 162.159.36.2
- C:\Users\<USER>\AppData\Local\Temp\_MEI33802\Crypto\Cipher\_ARC4.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI33802\Crypto\Cipher\_Salsa20.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI33802\Crypto\Cipher\_chacha20.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI33802\Crypto\Cipher\_pkcs1_decode.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI33802\Crypto\Cipher\_raw_aes.pyd
- Global\OneSettingQueryMutex+compat+encapsulation
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 6a99bc0128e0c7d6cbbf…cbc6c8Never scannednever seen before
- 98074c85650a420a095a…b084e9Never scannednever seen before
- 63d9bbdac4e8e2c95b1a…a57aeeNever scannednever seen before
- 4f05f31ca026bbfeeee4…7ab5deNever scannednever seen before
- 75687620596877b0dde4…8dde42Never scannednever seen before
- 804c60219443c2ea969e…ff590fNever scannednever seen before
- b60ce99ebcb7946fa9b6…fa5c58Never scannednever seen before
- 47576cae321c80e69c7f…ac6b91Never scannednever seen before
- 165be658ab7d61ffc3df…d3acd7Never scannednever seen before
- 6f6f3d25dad7d864ac3d…737706Never 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.
- 3rule hits recorded
- 7 / 75engines flagged
- 9sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
7 of 75 antivirus engines flagged the file, including APEX and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 10 times from 9 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: RebirthPub_SaveEditor (1).exe — ed1b9a5baf2fe4568abe3fe890dc8f9a552449c8502eb6d36008f65c398576f8
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\RebirthPub_SaveEditor.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\cmd.exe /c "ver"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: _ARC4.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI33802\Crypto\Cipher\_ARC4.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _Salsa20.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI33802\Crypto\Cipher\_Salsa20.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: generic-trojan
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for 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.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -pSandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exeThe 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.
Evidence162.159.36.2
7 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
- RebirthPub_SaveEditor (1).exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 15.3 MB
- Last analyzed
- Sep 4, 2026, 8:14 PM UTC
ed1b9a5baf2fe4568abe3fe890dc8f9a552449c8502eb6d36008f65c398576f8Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't run it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is RebirthPub_SaveEditor (1).exe safe, or is it malware?
What is RebirthPub_SaveEditor (1).exe?
How many antivirus engines detected RebirthPub_SaveEditor (1).exe?
I already downloaded and ran RebirthPub_SaveEditor (1).exe — what should I do?
How do I remove RebirthPub_SaveEditor (1).exe?
What kind of malware is RebirthPub_SaveEditor (1).exe?
What is the SHA-256 hash of RebirthPub_SaveEditor (1).exe?
How up to date is this analysis of RebirthPub_SaveEditor (1).exe?
Community
Member reviews and reports for this exact file hash.