File scan report
Verdict Safe
Is repak-
None of the 66 antivirus engines that checked it flagged this unsigned pak-manager tool, and its activity in the test run showed only log writes and connections to GitHub and…
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
This file can be used if it came from the official project release page. Keep your antivirus enabled and avoid copies from unofficial mirrors.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the developer's own website or an official app store.
Keep your antivirus and Windows updates switched on.
No scanner can promise a file is 100% safe.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 66 flagged
- Flagged 0
- No detection 66
- No result 9
- Code signing Unsigned
- Test run Completed
- First seen 1mo ago
Chapter 02
Why we think so
2 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The sandbox runs recorded no high-risk techniques. They recorded only an application log, a data file, and connections that fit an app checking GitHub for updates. The file is unsigned, so its publisher cannot be verified.
None of the 66 antivirus engines that checked it flagged the file, and 16 major antivirus engines returned clean results. The sandbox summary maps two techniques that often appear on clean software, but no injected process or defence tampering was recorded. The file wrote a log under its own application folder and a character data file, which fits a game pak management utility. Its network traffic went to IP ranges used by GitHub and Cloudflare, plus a certificate revocation check, rather than to unknown infrastructure. The main gap is the missing code signature, which leaves the publisher unconfirmed.
What We Detected
None of the 66 antivirus engines that checked it flagged this 20 MB 64-bit executable, and 16 major antivirus engines reported it clean. The file is not packed. It has been submitted by 55 distinct sources over about 46 days.
Threat Behavior
The sandbox runs recorded log and data file writes in the tool's own folders. Network connections went to GitHub and Cloudflare address ranges, plus a Let's Encrypt revocation check. No injected processes, persistence or malicious sandbox verdict were recorded. Two technique mappings appeared without any matching activity behind them. Only part of the contacted hosts could be checked against our reputation cache.
What To Do Now
If you obtained this tool from its official project page, it can be used normally. Because it is unsigned, download it only from the original source and keep your antivirus enabled.
Where this verdict could be wrong2 caveats
- The file is unsigned and has no publisher history, so its origin cannot be confirmed from a signature.
- Only one of the contacted hosts was checked against our reputation cache, so no complete host-reputation result is available.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the 66 antivirus engines that checked it flagged the file.
- 16 major antivirus engines explicitly reported it clean.
- No high-risk techniques, injection or persistence were recorded when it ran.
- The file is not packed or obfuscated.
- It has been seen from 55 different sources.
- The executable has no code signature, so its publisher cannot be verified.
- It connects directly to IP addresses, although these belong to GitHub and Cloudflare infrastructure.
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- 14sandbox rule tags
- 2spawned processes
- 5network contacts
- 8filesystem & mutex artifacts
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Techniques observed in the sandbox
14MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1027· Obfuscated code
- T1027.002· Obfuscated code
- T1036
- T1055· Process injection
- T1056· Keylogging
- T1071· Application protocol
- T1082· System recon
- T1095· Custom network
- T1105· Network file transfer
- T1497· Sandbox evasion
- T1518.001· Checks your AV
- T1562.001· Disables security
- T1573
- T1574· Execution hijack
Observed activity
Processes started
2Programs the file ran, with their command lines.
program.exe"C:\Users\<USER>\Desktop\program.exe"program.exe"C:\Users\user\Desktop\program.exe"
Network contacts
55 hosts, listed as 4 addresses, 1 link. Links show the host and path only.
- IP address
185.199.108.133 - IP address
104.18.20.213 - IP address
185.199.110.133 - IP address
104.18.21.213 - URL
http://yr1.c.lencr.org/127.crl
Files
8Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Roaming\repak_manager\latest.log - Written
C:\Users\<USER>\Desktop\data\character_data.json - Written
C:\Users\user\AppData\LocalLow\Microsoft\CryptnetUrlCache\Content\49A7F8B8A2FD8A9E65352CD7C88B1D10 - Written
C:\Users\user\AppData\LocalLow\Microsoft\CryptnetUrlCache\MetaData\49A7F8B8A2FD8A9E65352CD7C88B1D10 - Written
C:\Users\user\AppData\Roaming\repak_manager - Written
C:\Users\user\AppData\Roaming\repak_manager\latest.log
Show all 8 entries for files
- Written
C:\Users\user\Desktop\data - Written
C:\Users\user\Desktop\data\character_data.json
Files this sample writes at runtime
This file drops 3 children at runtime. None are currently flagged malicious in our cache. 3 have no saved verdict and were not checked; that is missing coverage, not a finding.
- 9e3db8a8735d5626722f…7c22feNot checkedno saved verdict
- 5bef060a478f8271a342…367a09Not checkedno saved verdict
- 8010ef8f59be34d63010…8c7691Not checkedno saved verdict
Chapter 04
Technical details
None of the 66 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.
File fingerprint
- Last analyzed
- Sep 12, 2026, 1:15 PM UTC
- SHA-256
c980bcb260536752f07a709db2a9fdb9bb03e3372b9b0da63bd1fd6aef8e6bab- SHA-1
fe376edb22b617ea8694ea3e0578eda5033e844a- MD5
eeccb33fe2033316759455a5eb628016
About this file
repak-gui.exe is a Win32 EXE file of 20.2 MB.
- Type and size
- Win32 EXE · 20.2 MB
- Signer
- UnsignedNo code signature.
- First seen
- Sep 6, 2026On VirusTotal.
- Submitted by
- 55 distinct sources
- Packer
- None detected
- Entropy
- 6.46 of 8
First scanned Updated
Verdict history
- Suspicious
- Safeafter a re-check of the saved evidence
Ratings change when antivirus engines, our checks or MalwareTips staff learn more about a file.
Antivirus consensus
0 of 66 engines flagged this file
9 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-116 engines0flagged
- Tier-234 engines0flagged
- Low-trust16 engines0flagged
View all 75 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleNo result
- GridinsoftClean
- huorongClean
- IkarusNo result
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingNo result
- SangforClean
- SentinelOneClean
- SkyhighNo result
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSNo result
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
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.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is repak-gui.exe safe?
What is repak-gui.exe?
How many antivirus engines detected repak-gui.exe?
What is the SHA-256 hash of repak-gui.exe?
Is it safe to run repak-gui.exe?
How up to date is this analysis of repak-gui.exe?
Community
Member reviews and reports for this exact file hash.