Malicious SHA-256 file hash 3910f46fe809… (OffSeq Mirage)
OffSeq Mirage honeypot sensors observed this SHA-256 file hash 4 time(s) in attacker activity between 2026-07-01 and 2026-07-01. Observed technique: T1105 (Ingress Tool Transfer). Seen from attacker infrastructure in PL. 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 payload fingerprinted by the SHA-256 hash 3910f46fe809d723d169b5723e0724dba7aed441a065b53b98e2f1b0a9736569 during attacker activity on 2026-07-01. The observed technique is T1105 (Ingress Tool Transfer), indicating the file was transferred into a target environment as part of an attack. The file may be a dropper, web shell, miner, or post-exploitation tool. The indicator serves as a detection artifact for defenders to identify this specific malicious file. No affected software versions or patches are specified, and no known exploits in the wild have been reported. The source infrastructure was located in Poland.
Potential Impact
The presence of this malicious file hash indicates potential compromise involving the transfer of a malicious payload into a target environment. The payload could enable attackers to deploy additional malicious tools such as droppers, web shells, miners, or post-exploitation utilities. However, there is no evidence of widespread exploitation or known active campaigns beyond the observed honeypot detections. The impact is limited to detection of this specific malicious file and its potential use in attacker operations.
Mitigation Recommendations
No vendor patch or official remediation is available or applicable for this indicator. Defenders should use this SHA-256 hash to match against files in their environments, endpoint detection and response (EDR) systems, antivirus (AV) solutions, and threat intelligence feeds. Detection and removal of files matching this hash is recommended to mitigate risk. Monitor for related attacker activity involving T1105 (Ingress Tool Transfer) techniques. No further specific mitigation actions are indicated by the source.
Indicators of Compromise
- hash: 3910f46fe809d723d169b5723e0724dba7aed441a065b53b98e2f1b0a9736569
Malicious SHA-256 file hash 3910f46fe809… (OffSeq Mirage)
Description
OffSeq Mirage honeypot sensors observed this SHA-256 file hash 4 time(s) in attacker activity between 2026-07-01 and 2026-07-01. Observed technique: T1105 (Ingress Tool Transfer). Seen from attacker infrastructure in PL. 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 payload fingerprinted by the SHA-256 hash 3910f46fe809d723d169b5723e0724dba7aed441a065b53b98e2f1b0a9736569 during attacker activity on 2026-07-01. The observed technique is T1105 (Ingress Tool Transfer), indicating the file was transferred into a target environment as part of an attack. The file may be a dropper, web shell, miner, or post-exploitation tool. The indicator serves as a detection artifact for defenders to identify this specific malicious file. No affected software versions or patches are specified, and no known exploits in the wild have been reported. The source infrastructure was located in Poland.
Potential Impact
The presence of this malicious file hash indicates potential compromise involving the transfer of a malicious payload into a target environment. The payload could enable attackers to deploy additional malicious tools such as droppers, web shells, miners, or post-exploitation utilities. However, there is no evidence of widespread exploitation or known active campaigns beyond the observed honeypot detections. The impact is limited to detection of this specific malicious file and its potential use in attacker operations.
Mitigation Recommendations
No vendor patch or official remediation is available or applicable for this indicator. Defenders should use this SHA-256 hash to match against files in their environments, endpoint detection and response (EDR) systems, antivirus (AV) solutions, and threat intelligence feeds. Detection and removal of files matching this hash is recommended to mitigate risk. Monitor for related attacker activity involving T1105 (Ingress Tool Transfer) techniques. No further specific mitigation actions are indicated by the source.
Technical Details
- Severity Source
- AI-assessed (no CVSS data)
Indicators of Compromise
Hash
| Value | Description | Copy |
|---|---|---|
hash3910f46fe809d723d169b5723e0724dba7aed441a065b53b98e2f1b0a9736569 | OffSeq Mirage — a malicious file, observed 2026-07-01..2026-07-01, 4× |
Threat ID: 6a45227f27e9c79719943e6a
Added to database: 07/01/2026, 14:21:51 UTC
Last enriched: 07/01/2026, 14:37:11 UTC
Last updated: 07/02/2026, 04:21:37 UTC
Views: 10
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.