Is DRT KEY SAMSUNG A02s.exe safe?
Thirty-five of 76 engines flagged this unsigned executable, including eight high-trust detections, while runtime evidence recorded process injection and direct-IP communication.
The evidence strongly indicates a generic Windows trojan associated with Malgent or AgentB labels. Microsoft and several other high-trust engines detected it, six YARA rules matched, and one sandbox run recorded T1055 process injection plus direct-IP traffic; the contacted addresses were not fully reputation-checked.
2b6bf1037ec582282a…0a12b8208cdf4fRecommended 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.
The evidence strongly indicates a generic Windows trojan associated with Malgent or AgentB labels. Microsoft and several other high-trust engines detected it, six YARA rules matched, and one sandbox run recorded T1055 process injection plus direct-IP traffic; the contacted addresses were not fully reputation-checked.
The executable was flagged by 35 of 76 engines, including eight high-trust detections, which is far beyond a low-trust false-positive pattern. Microsoft names Malgent, while BitDefender, Emsisoft, and GData converge on the same GenericKD identifier, although the payload does not report strong tier-1 family consensus. Static corroboration includes six YARAify matches, but some of those rules identify cryptographic constants or compiler traits and are not independently conclusive. The completed sandbox run recorded T1055 process injection and five direct-IP contacts, adding behavioral concern without producing an explicit malicious sandbox verdict. Because contactedHosts is unavailable, no complete reputation result exists for those addresses, and the unsigned status provides no publisher assurance.
What We Detected
Thirty-five of 76 antivirus engines flagged this Win32 executable. Eight high-trust engines detected it: Microsoft reported Trojan:Win32/Malgent!MTB, while BitDefender, Emsisoft, and GData reported Trojan.GenericKD.72238712. The file is unsigned, and six researcher-maintained YARA rules matched its static content.
Threat Behavior
One completed sandbox run mapped activity to MITRE T1055 process injection and observed communication with five IP addresses without application-domain contacts. That run did not issue an explicit malicious sandbox verdict, and it recorded no persistence indicators. A complete reputation cross-check was not available for the contacted addresses. Five dropped files were inspected, but their individual verdicts remain unknown.
What To Do Now
Do not execute the file. Quarantine or delete it with endpoint protection kept enabled; if it already ran, isolate the system, perform a full scan, and review running processes and outbound connections for follow-on activity.
Where this verdict could be wrong5 caveats
- engines.tier1FamilyConsensus.strong=false; the high-trust detections are mostly generic and do not establish one strong canonical family.
- behaviour.hasMaliciousSandboxVerdict=false, and no persistence indicators or registry changes were recorded in the single sandbox run.
- droppedChildren.hasMaliciousChild=false, but all five inspected children have unknown verdicts rather than confirmed benign results.
- peAnalysis.highEntropyCode=false and peAnalysis.likelyPacked=false, so the executable lacks common static packing indicators.
- similarHashes shows 1 prior 'suspicious' verdict for this imphash (matchKind=imphash, signerCoMatch=false), which is only weak context because installer-framework collisions are possible.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- behaviour.hasMaliciousSandboxVerdict=false
- No persistence indicators were recorded
- peAnalysis.highEntropyCode=false and peAnalysis.likelyPacked=false
- No dropped child was confirmed malicious
- 35/76 antivirus detections
- Eight high-trust engines flagged the executable
- Unsigned Windows executable
- Microsoft Malgent detection
- MITRE T1055 process-injection activity
- Five direct-IP contacts without a complete host-reputation check
Keep endpoint protection enabled and quarantine or remove the file rather than running it. If it was executed, isolate the device and perform a full endpoint and network investigation.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete35 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial5 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete7 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
- 12MITRE ATT&CK techniques
- 11spawned processes
- 5network contacts
- 31filesystem & 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.
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.
Moderate concern: Checks which security software you have installed.
Note: Collects details about your system.
Note: Loads extra code modules while running.
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
DRT KEY SAMSUNG A02s.exe
2b6bf1037ec582282af0eb774aae8a3b8bf965c102dceb1e790a12b8208cdf4f
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
%SAMPLEPATH%\2b6bf1037ec582282af0eb774aae8a3b8bf965c102dceb1e790a12b8208cdf4f.exe
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\System32\cmd.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
5.bat
C:\Documents and Settings\<USER>\Local Settings\Temp\3.tmp\4.tmp\5.bat
04Isolated runtime analysis - Written fileObserved
1
C:\Documents and Settings\<USER>\Application Data\1
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
a83f:8110:0:0:1b00:100:2800:0
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
13.107.4.50
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.
- a83f:8110:0:0:1b00:100:2800:0
- 13.107.4.50
- 23.216.147.76
- 20.22.113.133
- 192.229.211.108
- C:\Documents and Settings\<USER>\Local Settings\Temp\3.tmp\4.tmp\5.bat
- C:\Documents and Settings\<USER>\Application Data\1
- C:\Documents and Settings\<USER>\Application Data\emmcdl.exe
- C:\Users\<USER>\AppData\Local\Temp\63F0.tmp\6400.tmp\6401.bat
- C:\Users\<USER>\AppData\Roaming\1
- %USERPROFILE%\AppData\Roaming\com.txt
- %USERPROFILE%\AppData\Roaming\comp.txt
- %USERPROFILE%\AppData\Roaming\usb_comport.txt
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER22B5.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER2381.tmp.csv
- ShimCacheMutex
Files this sample writes at runtime
This file drops 5 children at runtime. None are currently flagged malicious in our cache.
- d0fe3d4d051b5b0e653b…4913b5Never scannednever seen before
- 536dc71c2c8b03cd0b0d…ab48e9Never scannednever seen before
- 5c41d24178e1c8f5cafd…c38cc3Never scannednever seen before
- e3b0c44298fc1c149afb…52b855Never scannednever seen before
- 63674dc615d157fd749e…983dc0Never 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.
- 7rule hits recorded
- 35 / 76engines flagged
- 11sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
6 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
35 of 76 antivirus engines flagged the file, including Alibaba and alibabacloud.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
YARAify matched 6 researcher rules to this file.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: DRT KEY SAMSUNG A02s.exe — 2b6bf1037ec582282af0eb774aae8a3b8bf965c102dceb1e790a12b8208cdf4f
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — %SAMPLEPATH%\2b6bf1037ec582282af0eb774aae8a3b8bf965c102dceb1e790a12b8208cdf4f.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\System32\cmd.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: 5.bat — C:\Documents and Settings\<USER>\Local Settings\Temp\3.tmp\4.tmp\5.bat
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 1 — C:\Documents and Settings\<USER>\Application Data\1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: a83f:8110:0:0:1b00:100:2800:0 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 13.107.4.50 — 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.
- DebuggerException__SetConsoleCtrl
- MD5_Constants
- PureBasic4xNeilHodgson
- RIPEMD160_Constants
- SHA1_Constants
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%SAMPLEPATH%\2b6bf1037ec582282af0eb774aae8a3b8bf965c102dceb1e790a12b8208cdf4f.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.
Evidencea83f:8110:0:0:1b00:100:2800:0 · 13.107.4.50 · 23.216.147.76
35 of 76 engines flagged this file
View all 76 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
- DRT KEY SAMSUNG A02s.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 467.5 KB
- Last analyzed
- Sep 16, 2026, 6:51 PM UTC
2b6bf1037ec582282af0eb774aae8a3b8bf965c102dceb1e790a12b8208cdf4fSafety & 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 you typed any passwords while it was open, change them from a device you trust.
- 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 DRT KEY SAMSUNG A02s.exe a virus?
What is DRT KEY SAMSUNG A02s.exe?
How many antivirus engines detected DRT KEY SAMSUNG A02s.exe?
What should I do if I already ran DRT KEY SAMSUNG A02s.exe?
How do I remove DRT KEY SAMSUNG A02s.exe?
What kind of malware is DRT KEY SAMSUNG A02s.exe?
What is the SHA-256 hash of DRT KEY SAMSUNG A02s.exe?
How up to date is this analysis of DRT KEY SAMSUNG A02s.exe?
Community
Member reviews and reports for this exact file hash.