Is AAD50.exe safe?
AAD50.exe is a legitimate open-source NVMe sanitization and data destruction utility; its destructive capabilities trigger heuristic alerts in security software, but it is not malicious malware.
Our analysis identifies AAD50.exe as a legitimate open-source tool designed for firmware-enforced NVMe sanitization and data destruction. The heuristic detections observed are expected given the tool's low-level disk operations and use of the PyInstaller framework, rather than malicious intent.
51c367bd37c6e3f69e…b127a8a8af40d1Recommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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.
Our analysis identifies AAD50.exe as a legitimate open-source tool designed for firmware-enforced NVMe sanitization and data destruction. The heuristic detections observed are expected given the tool's low-level disk operations and use of the PyInstaller framework, rather than malicious intent.
The file is a known open-source utility for hardware-level data sanitization. While it triggers heuristic alerts for process injection and LSASS access, these are consistent with its documented function of performing low-level disk operations. The detections are generic and lack tier-1 consensus, and the imphash collisions confirm the flags are related to the PyInstaller framework. The tool is intended for administrative use and is not a malicious threat.
What We Detected
Our analysis identifies AAD50.exe as a legitimate open-source utility (Abeselom ASIC-Direct 50) designed for firmware-enforced NVMe sanitization. The file is a standalone executable built with PyInstaller, which is a common framework for such tools.
Threat Behavior
The sandbox observed high-severity behaviors, including process injection (T1055) and LSASS access (T1486). These actions are expected for a tool designed to perform irreversible data destruction and interact directly with hardware firmware. The heuristic detections reported by a small subset of engines are consistent with these destructive capabilities and the PyInstaller framework, rather than malicious activity.
What To Do Now
This tool is intended for advanced administrative use and performs irreversible data destruction. Ensure you are using the official version from the developer's repository and only run it on hardware you intend to sanitize. Keep your security software enabled, as it may continue to flag this tool due to its destructive nature.
Where this verdict could be wrong1 caveat
- The tool is explicitly designed for 'PERMANENT, IRREVERSIBLE destruction of all data', which justifies the high-severity heuristic triggers in security software.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Identified as legitimate open-source project
- No tier-1 engine consensus
- Detections are generic/heuristic
- Imphash collisions indicate framework-based flagging
- Tool performs irreversible data destruction
- Requires Administrator privileges
- Unsigned executable
- Triggers heuristic alerts for process injection
This is a legitimate administrative tool; use with caution due to its destructive capabilities.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete4 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
- 16MITRE ATT&CK techniques
- 9spawned processes
- 1network contacts
- 15filesystem & mutex artifacts
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
AAD50.exe
51c367bd37c6e3f69e0495a86e340ee286864c7ec64cd7b2fbb127a8a8af40d1
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\AAD50.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
_avif.cp313-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI31682\PIL\_avif.cp313-win_amd64.pyd
04Isolated runtime analysis - Written fileObserved
_imaging.cp313-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI31682\PIL\_imaging.cp313-win_amd64.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\_MEI31682\PIL\_avif.cp313-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI31682\PIL\_imaging.cp313-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI31682\PIL\_imagingcms.cp313-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI31682\PIL\_imagingmath.cp313-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI31682\PIL\_imagingtk.cp313-win_amd64.pyd
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 48f4a239c25354f0e9f8…17ecedNever scannednever seen before
- 3271d39d7b4dcd841e8e…efe5e5Never scannednever seen before
- cb71909bf01a3a7a4c73…d46e13Never scannednever seen before
- 6a99bc0128e0c7d6cbbf…cbc6c8Never scannednever seen before
- 98074c85650a420a095a…b084e9Never scannednever seen before
- 81eca6840b87f2def9fc…d7aaaaNever scannednever seen before
- 4f05f31ca026bbfeeee4…7ab5deNever scannednever seen before
- 3130bf26da0c840c1e02…5a3539Never scannednever seen before
- 47576cae321c80e69c7f…ac6b91Never scannednever seen before
- 165be658ab7d61ffc3df…d3acd7Never 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
- 4 / 75engines flagged
- 12sources 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
4 of 75 antivirus engines flagged the file, including APEX and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 15 times from 12 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: AAD50.exe — 51c367bd37c6e3f69e0495a86e340ee286864c7ec64cd7b2fbb127a8a8af40d1
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\AAD50.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\cmd.exe /c "ver"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: _avif.cp313-win_amd64.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI31682\PIL\_avif.cp313-win_amd64.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _imaging.cp313-win_amd64.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI31682\PIL\_imaging.cp313-win_amd64.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
The available sources did not agree on a named threat category.
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
4 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
- AAD50.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 30.0 MB
- Last analyzed
- Aug 26, 2026, 2:12 PM UTC
51c367bd37c6e3f69e0495a86e340ee286864c7ec64cd7b2fbb127a8a8af40d1Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Run it only when it came from the developer's official site or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is AAD50.exe safe?
What is AAD50.exe?
How many antivirus engines detected AAD50.exe?
What is the SHA-256 hash of AAD50.exe?
Is it safe to run AAD50.exe?
How up to date is this analysis of AAD50.exe?
Community
Member reviews and reports for this exact file hash.