Is SoffysRebrandv2_3.exe safe?
Unsigned 15 MB PyInstaller EXE with nine tier-1 detections, four offensive MITRE techniques, and prior imphash matches flagged suspicious.
Nine tier-1 engines flag the sample as malicious across multiple generic-trojan families. Sandbox evidence shows process injection, data destruction, and persistence techniques. Two of three similar imphash files were previously marked suspicious.
ce3059cb47ea543240…765e2c2f871838Recommended 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.
Nine tier-1 engines flag the sample as malicious across multiple generic-trojan families. Sandbox evidence shows process injection, data destruction, and persistence techniques. Two of three similar imphash files were previously marked suspicious.
The file is unsigned despite being a 15 MB PE, removing any trusted-publisher benefit. Nine tier-1 engines independently detect it, and the sandbox recorded T1055 process injection plus T1485/T1486 destructive behaviour. Similar imphash matches have already produced suspicious verdicts, and community tags reference known credential-stealer families. The combination of tier-1 consensus, offensive MITRE techniques, and prior suspicious imphash matches outweighs the single safe RAG outlier.
What We Detected
34 of 75 engines flag the file malicious; nine of those are tier-1 vendors. The most common families cited are Wacatac, Agent, USBLE726, and generic trojan labels. The sample is unsigned and shows high-entropy sections consistent with PyInstaller packaging.
Threat Behavior
Sandbox execution recorded process injection (T1055), file deletion/wiping (T1485/T1486), and persistence via startup mechanisms (T1547.001). Twenty direct-IP connections were made with no domain resolution, a pattern also seen in prior suspicious imphash matches.
What To Do Now
Do not execute the file. Keep endpoint protection enabled and submit the sample to your security vendor for further family classification. Review any systems that may have run the executable for persistence artifacts and credential theft indicators.
Where this verdict could be wrong1 caveat
- similarHashes[2] returned safe verdict (ai:low_trust_engines_only) on same imphash — weak counter-signal.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Unsigned executable
- Nine tier-1 malicious detections
- Process injection and data-wiping techniques observed
- Direct-IP C2 traffic pattern
- Prior imphash matches flagged suspicious
Treat the file as malicious; block its hash and monitor affected hosts for credential-theft or ransomware activity.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete34 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial20 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete2 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
- 20MITRE ATT&CK techniques
- 9spawned processes
- 20network contacts
- 30filesystem & 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: Changed an auto-start location that can make code run after sign-in or restart.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
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
SoffysRebrandv2_3.exe
ce3059cb47ea543240278970abd7bb8523615ad12924559248765e2c2f871838
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\SoffysRebrandv2_3.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
VCRUNTIME140.dll
C:\Users\<USER>\AppData\Local\Temp\_MEI60562\VCRUNTIME140.dll
04Isolated runtime analysis - Written fileObserved
VCRUNTIME140_1.dll
C:\Users\<USER>\AppData\Local\Temp\_MEI60562\VCRUNTIME140_1.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
140.82.114.4
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
185.199.109.133
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.
- 140.82.114.4
- 185.199.109.133
- 185.199.110.153
- 64.239.123.65
- 13.107.213.38
- 150.171.73.13
- 13.107.246.38
- 130.211.47.218
- 34.160.81.0
- 172.66.166.164
- C:\Users\<USER>\AppData\Local\Temp\_MEI60562\VCRUNTIME140.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI60562\VCRUNTIME140_1.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI60562\_asyncio.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI60562\_bz2.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI60562\_ctypes.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI60562\base_library.zip
- C:\Users\<USER>\AppData\Local\Temp\_MEI60562\certifi\cacert.pem
- C:\Users\<USER>\AppData\Local\Temp\_MEI60562\certifi\py.typed
- C:\Users\<USER>\AppData\Local\Temp\_MEI60562\certifi
- C:\Users\<USER>\AppData\Local\Temp\_MEI60562\charset_normalizer\md.cp314-win_amd64.pyd
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- d199dd3188c2ba0f8f04…c26404Never scannednever seen before
- b68b04957c3f76cdaac4…cad0b0Never scannednever seen before
- 03b4a25a32969117d8c9…00da32Never scannednever seen before
- 536a3b521a3c42d2827e…1266d4Never scannednever seen before
- 7214c0619e2133d0c44a…f30f48Never scannednever seen before
- a444a932b950e520374a…f86669Never scannednever seen before
- 04738ee6b96bcc635144…b56b80Never scannednever seen before
- b2a2d4848c89d6a60309…d95dc5Never scannednever seen before
- 43e60bbdff2fe41701f3…5e648fNever scannednever seen before
- 494c3609d53bd786435a…fd893cNever 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.
- 2rule hits recorded
- 34 / 75engines flagged
- 46sources 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
34 of 75 antivirus engines flagged the file, including alibabacloud and ALYac.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 57 times from 46 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: SoffysRebrandv2_3.exe — ce3059cb47ea543240278970abd7bb8523615ad12924559248765e2c2f871838
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\SoffysRebrandv2_3.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\cmd.exe /c "ver"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: VCRUNTIME140.dll — C:\Users\<USER>\AppData\Local\Temp\_MEI60562\VCRUNTIME140.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: VCRUNTIME140_1.dll — C:\Users\<USER>\AppData\Local\Temp\_MEI60562\VCRUNTIME140_1.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 140.82.114.4 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 185.199.109.133 — 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.
Evidence"C:\Users\<USER>\Desktop\SoffysRebrandv2_3.exe"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.
Evidence140.82.114.4 · 185.199.109.133 · 185.199.110.153
34 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
- SoffysRebrandv2_3.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 14.5 MB
- Last analyzed
- Aug 9, 2026, 6:13 AM UTC
ce3059cb47ea543240278970abd7bb8523615ad12924559248765e2c2f871838Safety & 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 any of your files were locked or renamed, do NOT pay the ransom — payment rarely restores files. Recover them from a backup instead.
- 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 SoffysRebrandv2_3.exe malware?
What is SoffysRebrandv2_3.exe?
How many antivirus engines detected SoffysRebrandv2_3.exe?
I already downloaded and ran SoffysRebrandv2_3.exe — what should I do?
How do I remove SoffysRebrandv2_3.exe?
What kind of malware is SoffysRebrandv2_3.exe?
What is the SHA-256 hash of SoffysRebrandv2_3.exe?
How up to date is this analysis of SoffysRebrandv2_3.exe?
Community
Member reviews and reports for this exact file hash.