Malicious SHA-256 file hash 44689d3e1a7f… (OffSeq Mirage)
OffSeq Mirage honeypot sensors observed this SHA-256 file hash 2 time(s) in attacker activity between 2026-07-09 and 2026-07-09. Observed technique: T1105 (Ingress Tool Transfer). Seen from attacker infrastructure in GB. File hashes fingerprint a specific malicious payload (a dropper, web shell, miner, or post-exploitation tool) that was staged or delivered during the attack. Match it against files in your environment and your EDR/AV and threat-intel feeds.
AI Analysis
Technical Summary
OffSeq Mirage honeypot sensors detected a malicious file with SHA-256 hash 44689d3e1a7f460db2ecc14351c171f4910721257f83024c63cbc07f4e2b977c during attacker activity on 2026-07-09. The activity involved the T1105 technique, which is used for ingress tool transfer, suggesting the file was used to stage or deliver a malicious payload. The file may represent various types of malware including droppers, web shells, miners, or post-exploitation tools. The attacker infrastructure was identified in Great Britain. There is no information on specific affected software versions or known exploits in the wild. This is an indicator of compromise (IOC) useful for detection and response.
Potential Impact
The presence of this malicious file hash indicates potential compromise involving the transfer and deployment of malicious payloads such as droppers, web shells, miners, or post-exploitation tools. This can lead to unauthorized access, persistence, data theft, or resource abuse. However, no confirmed exploitation or widespread attacks using this file have been reported.
Mitigation Recommendations
No official patches or fixes are applicable as this is an indicator of compromise rather than a vulnerability in software. Security teams should use this SHA-256 hash to scan and detect the presence of the malicious file within their environments using endpoint detection and response (EDR), antivirus (AV), and threat intelligence feeds. Blocking or quarantining files matching this hash and investigating related activity is recommended. Monitor for ingress tool transfer techniques (T1105) and strengthen controls around file transfers from untrusted sources.
Indicators of Compromise
- hash: 44689d3e1a7f460db2ecc14351c171f4910721257f83024c63cbc07f4e2b977c
Malicious SHA-256 file hash 44689d3e1a7f… (OffSeq Mirage)
Description
OffSeq Mirage honeypot sensors observed this SHA-256 file hash 2 time(s) in attacker activity between 2026-07-09 and 2026-07-09. Observed technique: T1105 (Ingress Tool Transfer). Seen from attacker infrastructure in GB. File hashes fingerprint a specific malicious payload (a dropper, web shell, miner, or post-exploitation tool) that was staged or delivered during the attack. Match it against files in your environment and your EDR/AV and threat-intel feeds.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
OffSeq Mirage honeypot sensors detected a malicious file with SHA-256 hash 44689d3e1a7f460db2ecc14351c171f4910721257f83024c63cbc07f4e2b977c during attacker activity on 2026-07-09. The activity involved the T1105 technique, which is used for ingress tool transfer, suggesting the file was used to stage or deliver a malicious payload. The file may represent various types of malware including droppers, web shells, miners, or post-exploitation tools. The attacker infrastructure was identified in Great Britain. There is no information on specific affected software versions or known exploits in the wild. This is an indicator of compromise (IOC) useful for detection and response.
Potential Impact
The presence of this malicious file hash indicates potential compromise involving the transfer and deployment of malicious payloads such as droppers, web shells, miners, or post-exploitation tools. This can lead to unauthorized access, persistence, data theft, or resource abuse. However, no confirmed exploitation or widespread attacks using this file have been reported.
Mitigation Recommendations
No official patches or fixes are applicable as this is an indicator of compromise rather than a vulnerability in software. Security teams should use this SHA-256 hash to scan and detect the presence of the malicious file within their environments using endpoint detection and response (EDR), antivirus (AV), and threat intelligence feeds. Blocking or quarantining files matching this hash and investigating related activity is recommended. Monitor for ingress tool transfer techniques (T1105) and strengthen controls around file transfers from untrusted sources.
Technical Details
- Severity Source
- AI-assessed (no CVSS data)
Indicators of Compromise
Hash
| Value | Description | Copy |
|---|---|---|
hash44689d3e1a7f460db2ecc14351c171f4910721257f83024c63cbc07f4e2b977c | OffSeq Mirage — a malicious file, observed 2026-07-09..2026-07-09, 2× |
Threat ID: 6a4f91fb68715ace435638dd
Added to database: 07/09/2026, 12:20:11 UTC
Last enriched: 07/09/2026, 12:32:41 UTC
Last updated: 07/10/2026, 03:33:03 UTC
Views: 12
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.