Is project.exe safe?
Eight tier-1 engines and 22 YARA rules flag this unsigned 64-bit PE as GenKryptik.
39 of 75 engines detect the file, including eight tier-1 detections converging on GenKryptik. The sample is unsigned, exhibits two offensive MITRE techniques, and matches 22 community YARA rules.
5d4ad3e19d7bd5da58…37e87db967cccdRecommended 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.
39 of 75 engines detect the file, including eight tier-1 detections converging on GenKryptik. The sample is unsigned, exhibits two offensive MITRE techniques, and matches 22 community YARA rules.
Tier-1 consensus on the GenKryptik family, combined with a high volume of YARA rule matches, outweighs the absence of sandbox malice and incomplete host-reputation data. The file is unsigned and shows privilege-escalation and defense-evasion techniques. Medium prevalence and lack of trusted signer history further support the malicious classification.
What We Detected
39 of 75 engines flagged the 25 MB Win32 EXE. Eight tier-1 engines (Avast, AVG, BitDefender, Emsisoft, ESET-NOD32, Fortinet, GData, Microsoft, Sophos, Symantec, TrendMicro) returned GenKryptik or Yogi family labels. YARAify matched 22 rules, five of which fired in our heuristics.
Threat Behavior
Static analysis shows two offensive MITRE techniques (T1134 token manipulation, T1562.001 disable security tools). The sample wrote temporary files and contacted one external IP address; sandbox execution produced no malicious verdict. No dropped child files were flagged malicious.
What To Do Now
Quarantine or delete the file. Do not execute it. Keep endpoint protection enabled and scan any systems that ran or received the sample.
Where this verdict could be wrong2 caveats
- contactedHosts=null — host-reputation cross-check incomplete.
- droppedChildren.hasMaliciousChild=false
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- no malicious dropped children
- sandbox returned no malicious verdict
- 8 tier-1 malicious detections
- 22 YARA rule matches
- unsigned executable
- offensive MITRE techniques T1134, T1562.001
Remove the file and scan the host with current signatures; monitor for any persistence mechanisms left behind.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete39 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
Complete6 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
- 18MITRE ATT&CK techniques
- 4spawned processes
- 1network contacts
- 11filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Used an input-capture technique that can record credentials or keystrokes.
High concern: Attempted to impair or bypass security controls.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Scans through your files and folders.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Note: Collects details about your system.
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
project.exe
5d4ad3e19d7bd5da58e294dff1e4c5f47fa65bfb208581a96537e87db967cccd
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
cmd.exe /d /c exit 0
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\project.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
obseswiee_preflight_00000A40.tmp
C:\Users\<USER>\AppData\Local\Temp\obseswiee_preflight_00000A40.tmp
04Isolated runtime analysis - Written fileObserved
Volumeid.exe
C:\Users\<USER>\AppData\Local\Temp\obseswieeMem_0003977E_2624\Volumeid.exe
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\obseswiee_preflight_00000A40.tmp
- C:\Users\<USER>\AppData\Local\Temp\obseswieeMem_0003977E_2624\Volumeid.exe
- C:\Users\user\AppData\Local\Temp\obseswieeMem_004D3D8F_7124\
- C:\Users\user\AppData\Local\Temp\obseswieeMem_004D3D8F_7124\Volumeid.exe
- C:\Users\user\AppData\Local\Temp\obseswiee_preflight_00001BD4.tmp
- C:\Users\<USER>\AppData\Local\Temp\obseswiee_preflight_00000A40.tmp
- C:\Users\<USER>\AppData\Local\Temp\obseswieeMem_0003977E_2624\Volumeid.exe
- C:\Users\user\AppData\Local\Temp\obseswieeMem_004D3D8F_7124
- C:\Users\user\AppData\Local\Temp\obseswieeMem_004D3D8F_7124\Volumeid.exe
- C:\Users\user\AppData\Local\Temp\obseswiee_preflight_00001BD4.tmp
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache.
- 22a2484d7fa799e6e71e…8a72f3Never scannednever seen before
- 6070a1c86f3f692aed2d…471fd2Never 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.
- 6rule hits recorded
- 39 / 75engines flagged
- 24sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
5 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceObservedSourceSignature and behavior rulesObserved at - 02
39 of 75 antivirus engines flagged the file, including Alibaba and alibabacloud.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
YARAify matched 22 researcher rules to this file.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: project.exe — 5d4ad3e19d7bd5da58e294dff1e4c5f47fa65bfb208581a96537e87db967cccd
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — cmd.exe /d /c exit 0
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\user\Desktop\project.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: obseswiee_preflight_00000A40.tmp — C:\Users\<USER>\AppData\Local\Temp\obseswiee_preflight_00000A40.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Volumeid.exe — C:\Users\<USER>\AppData\Local\Temp\obseswieeMem_0003977E_2624\Volumeid.exe
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
One or more independent reference databases matched 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.
- Any_SU_Domain
- CarbonOrchestrator_v3_77_
- CarbonOrchestrator_v3_79_
- CarbonOrchestrator_v3_81_
- CMD_Shutdown
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.
Evidence162.159.36.2
39 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
- project.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 23.9 MB
- Last analyzed
- Aug 30, 2026, 11:32 PM UTC
5d4ad3e19d7bd5da58e294dff1e4c5f47fa65bfb208581a96537e87db967cccdSafety & 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
From a different, clean device, change the passwords on your important accounts (email and banking first) and turn on two-factor authentication.
- 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 project.exe malware?
What is project.exe?
How many antivirus engines detected project.exe?
I already downloaded and ran project.exe — what should I do?
How do I remove project.exe?
What kind of malware is project.exe?
What is the SHA-256 hash of project.exe?
How up to date is this analysis of project.exe?
Community
Member reviews and reports for this exact file hash.