- First seen
- Last seen
Indicator overview
INDICATOR PROFILEEngine detections are elevated in this report. Review the reported confidence, classification and relationships alongside them.
- SHA256
1d80331fddf9f2b14b636fc3f214cbac348892d8d033c23d9ae213e2b0777943- SHA1
73e13948d7cdad12948a9cf03b8a43cc1c49d9bf- MD5
4261083271f4aa91928011fe114c99b5- Filename
- oej2z.exe
- File type
- elf
- MIME
- application/x-elf
- File size
- 60444
- Filename variants
- 3 reported
- TLSH
T1A0430752BC818A16C6E0527AF92E85CE3B2123E8E2DF73079D211F6176CB41F0D67D96- SSDEEP
1536:Q64i29YzaK1r5mTPAzHcEe7X1suV27cbhMDHs:Q6ia7d41b270hq
Connected context
Key findings
OBSERVED EVIDENCEElevated engine detections. Related indicators in this report: 3. Review the supporting evidence before taking action.
Malicious. Engine detections are elevated at 71%.
VirusSign reports 100% confidence. Review this alongside engine detections and relationship evidence.
Analysis signals
OBSERVEDExpand a connection to run an additional public query. This page allows up to 3 expansions; each counts toward your query limit.
Compare when indicators were first seen, last seen and observed. Switch to Lifecycle to connect events for the same IOC.
Review approximate infrastructure locations and geographic concentration.
No observations in this view
Available evidence appears in the other investigation lenses.
Visible connections
Related intelligence
Pivot across connected files and infrastructure with analysis signals and supporting context.
Dropped / child files
Files dropped, bundled, or created by the queried file.
Related IPs
Network IPs associated with this indicator.
Analysis details
Freshness: Fresh · Last seen today.
- Detection rate
- 71%
- Threat type
- trojan
- Family
- mirai
- Confidence
- 100%
- detection
- 71 · Engine detection rate; color may also reflect VirusSign confidence.
Overview
- SHA256
1d80331fddf9f2b14b636fc3f214cbac348892d8d033c23d9ae213e2b0777943- SHA1
73e13948d7cdad12948a9cf03b8a43cc1c49d9bf- MD5
4261083271f4aa91928011fe114c99b5- Filename
- oej2z.exe
- File type
- elf
- MIME
- application/x-elf
- File size
- 60444
- TLSH
T1A0430752BC818A16C6E0527AF92E85CE3B2123E8E2DF73079D211F6176CB41F0D67D96- SSDEEP
1536:Q64i29YzaK1r5mTPAzHcEe7X1suV27cbhMDHs:Q6ia7d41b270hq- First seen
- 2026-11-12T20:04:56Z
- Last seen
- 2026-11-13T00:46:37Z
- Filename variants
- 3 reported
Key findings
A focused interpretation of the evidence, relationships and observation history that matter most.
Elevated engine detections. Related indicators in this report: 3. Review the supporting evidence before taking action.
Malicious. Engine detections are elevated at 71%.
VirusSign reports 100% confidence. Review this alongside engine detections and relationship evidence.
Classification includes type trojan and family mirai.
3 related indicators are shown across 2 relationship group(s).
4 timestamped observations are arranged from 2013-02-24 to 2026-11-12. These are observation or metadata times, not execution order.
Why this verdict
Review the reported detections, analysis confidence and supporting context.
Engine detections are elevated in this report. Review the reported confidence, classification and relationships alongside them.
Reported engine detection rate, not the probability that this indicator is malicious.
VirusSign analysis confidence; separate from detection rate and actor-association confidence.
2 relationship group(s) provide pivot and infrastructure context.
Classification context: type trojan, family mirai.
Last seen today.
Signals reflect the intelligence returned in this report. Missing values mean not reported, not zero. Related indicators are investigation leads, not proof of shared malicious activity.
File profile
summarySelected file intelligence summary.
- Filename
- oej2z.exe
- File type
- elf
- MIME
- application/x-elf
- Size
- 60444
Observed behavior
selected detailsSelected behavioral observations and reported framework mappings.
View details · 5 shown
- Classification label
- Connects to IPs without corresponding DNS lookups
- Detected TCP or UDP traffic on non-standard ports
- Malicious sample detected (through community Yara rule)
- May try to detect the virtual machine to hinder analysis (VM artifact strings found in memory)
View MITRE ATT&CK details · 5 shown
- T1571 — Detected TCP or UDP traffic on non-standard portsTactics: TA0011
- T1027.008 — Sample has stripped symbol tableTactics: TA0005
- T1205.002 — Sample listens on a socketTactics: TA0003 · TA0005 · TA0011
- T1497.001 — Static ELF header machine description suggests that the sample might not execute correctly on this machine.Tactics: TA0005 · TA0007
- T1082 — Static ELF header machine description suggests that the sample might only run correctly on MIPS or ARM architectures.Tactics: TA0007
Network activity
selected detailsSelected observations and details. Additional structured data are available through API and data access.
- 2 outbound connections observed
- 0 domains, 1 IPs, 0 URLs
- Common ports: 61231
- Protocols: TCP
View details · 2 shown
- IP
- 181.215.115.186
- Port
- 61231
- IP
- 181.215.115.186
- Port
- 61231
- Protocol
- TCP
- 2 C2 candidate communications
- 0 domains, 1 IPs
- Common ports: 61231
- Protocols: TCP
View details · 2 shown
- IP
- 181.215.115.186
- Port
- 61231
- Protocol
- TCP
- IP
- 181.215.115.186
- Port
- 61231