Is LMAOBOXLOADER.exe safe?
Forty-two of 76 engines flagged this unsigned, packed executable, with three tier-1 engines agreeing on Rogue and runtime evidence showing defense impairment.
The evidence strongly associates this executable with the Rogue trojan family: 42 of 76 engines detected it, including 11 tier-1 votes and three tier-1 Rogue labels. It is also unsigned, packed, and exhibited T1562.001 plus direct-IP network activity during one sandbox run; the contacted IPs were not reputation-checked completely.
17155782d239ac1379…2b7cac637d3c59Recommended 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 associates this executable with the Rogue trojan family: 42 of 76 engines detected it, including 11 tier-1 votes and three tier-1 Rogue labels. It is also unsigned, packed, and exhibited T1562.001 plus direct-IP network activity during one sandbox run; the contacted IPs were not reputation-checked completely.
A broad 42/76 engine detection ratio includes 11 independent tier-1 malicious votes, which is far beyond a low-trust false-positive pattern. Avira, F-Secure, and Ikarus agree on the Rogue family, satisfying strong tier-1 family consensus. Microsoft and SUPERAntiSpyware instead identify Bladabindi, so the exact family has some disagreement even though the harmful nature is strongly corroborated. Static analysis shows an unsigned, likely packed .NET executable with a 7.82-entropy code section. One sandbox run observed T1562.001 and three direct-IP connections, but no complete host-reputation result is available because the contacted-host cross-check was not saved. Its age, prevalence, and positive reputation are meaningful counter-signals, yet they do not outweigh the engine consensus and supporting technical evidence.
What We Detected
Forty-two of 76 antivirus engines flagged the executable. Eleven OEM-deduplicated tier-1 engines contributed malicious votes, and Avira, F-Secure, and Ikarus independently used Rogue-family labels. Microsoft reported Backdoor:Win32/Bladabindi!ml, while other engines supplied generic trojan, PUA, or Sdum labels; this disagreement affects the precise family name but not the overall risk assessment.
Threat Behavior
The executable is unsigned and peAnalysis.likelyPacked=true, with entropy 7.82 in its .text section, indicating substantial code packing or obfuscation. One completed sandbox run observed T1562.001, a technique involving impairment of defensive controls, and connections to 20.99.184.37, 23.216.147.76, and 20.80.129.13. The contacted-host reputation check was not completed or retained, so those endpoints cannot be described as clean or known-malicious from this evidence alone. No malicious child file or explicit malicious sandbox verdict was recorded.
What To Do Now
Do not run the executable, and keep endpoint protection enabled. Quarantine or remove it, then perform a full system scan; if it has already executed, isolate the device from the network and investigate the three contacted IP addresses, running processes, startup locations, and account activity.
Where this verdict could be wrong4 caveats
- The file is old and widely encountered: prevalence.uniqueSources=172, prevalence.timesSubmitted=183, and file.reputation=94.
- behaviour.hasMaliciousSandboxVerdict=false, although one run observed defense impairment and direct-IP traffic.
- externalIntel.yaraify.ruleCount=0, externalIntel.malwareBazaar.hit=false, and externalIntel.circl.hit=false; these absences do not outweigh the engine consensus.
- The engine labels differ beyond the Rogue consensus, including Bladabindi, Sdum, GameHack, PUA, and generic detections, limiting confidence in the precise family identity.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Observed since 2013 and submitted by 172 distinct sources
- file.reputation=94
- behaviour.hasMaliciousSandboxVerdict=false
- No malicious dropped child was recorded
- MalwareBazaar, CIRCL, and YARAify returned no hits
- 42/76 engines reported malicious findings
- 11 OEM-deduplicated tier-1 malicious votes
- Strong three-engine tier-1 consensus on Rogue
- Unsigned Windows executable
- Likely packed code with .text entropy 7.82
- Sandbox-observed T1562.001 defense impairment
Quarantine or delete the file without executing it, and keep all security protection enabled. If it has run, disconnect the system from the network and conduct a full endpoint and credential-compromise investigation.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete42 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial3 runtime contacts were 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
- 6MITRE ATT&CK techniques
- 1spawned processes
- 3network contacts
- 16filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Attempted to impair or bypass security controls.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Note: Listed running processes; both legitimate software and malware may do this.
Note: Collects details about your system.
Note: Connected to 3 servers during sandbox analysis.
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
LMAOBOXLOADER.exe
17155782d239ac1379b2cb38ee74060349499ec9f3738b2c982b7cac637d3c59
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
%SAMPLEPATH%\17155782d239ac1379b2cb38ee74060349499ec9f3738b2c982b7cac637d3c59.exe
02Isolated runtime analysis
Files
Created or changed
- Written fileObserved
Roaming
C:\Users\user\AppData\Roaming
03Isolated runtime analysis
Network
Hosts contacted
- Contacted hostObserved
20.99.184.37
Contact observed during runtime.
04Isolated runtime analysis - Contacted hostObserved
23.216.147.76
Contact observed during runtime.
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- 20.99.184.37
- 23.216.147.76
- 20.80.129.13
- C:\Users\user\AppData\Roaming
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5DE.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERD6A9.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERD717.tmp.txt
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER175B.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER175D.tmp.csv
- CTF.LBES.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Compart.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Asm.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Layouts.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.TMD.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
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
- 42 / 76engines flagged
- 172sources 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
42 of 76 antivirus engines flagged the file, including AhnLab-V3 and APEX.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has a long, established submission history across 172 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: LMAOBOXLOADER.exe — 17155782d239ac1379b2cb38ee74060349499ec9f3738b2c982b7cac637d3c59
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — %SAMPLEPATH%\17155782d239ac1379b2cb38ee74060349499ec9f3738b2c982b7cac637d3c59.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: Roaming — C:\Users\user\AppData\Roaming
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: 20.99.184.37 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 23.216.147.76 — 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.
PE is packed (high-entropy code or known packer) AND unsigned AND at least one engine flagged it. Packing alone is common in legit software; packing + unsigned + signal is the malware-dropper pattern.
Evidencepackers: .NET executableThe 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.
Evidence20.99.184.37 · 23.216.147.76 · 20.80.129.13Unsigned, packed PE with sandbox-observed network activity. The packing step hides the payload until execution; the network call fetches / reports for the next stage. Classic dropper / stager behaviour.
Evidence20.99.184.37
42 of 76 engines flagged this file
View all 76 engine results
Section entropy & packers
Executable sections have high entropy (7.2+) — the code is compressed or encrypted and only decrypted at runtime. Classic packing behaviour.
Packers compress or encrypt the executable and only unpack it at runtime. Legitimate commercial software uses them too — but if the file is also unsigned and rare, it's a strong malware signal.
How widely this file has been seen
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- LMAOBOXLOADER.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 164.5 KB
- Last analyzed
- Sep 30, 2026, 9:06 PM UTC
17155782d239ac1379b2cb38ee74060349499ec9f3738b2c982b7cac637d3c59Safety & 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 LMAOBOXLOADER.exe malware?
What is LMAOBOXLOADER.exe?
How many antivirus engines detected LMAOBOXLOADER.exe?
I already downloaded and ran LMAOBOXLOADER.exe — what should I do?
How do I remove LMAOBOXLOADER.exe?
What kind of malware is LMAOBOXLOADER.exe?
What is the SHA-256 hash of LMAOBOXLOADER.exe?
How up to date is this analysis of LMAOBOXLOADER.exe?
Community
Member reviews and reports for this exact file hash.