A malicious file identified by the SHA-256 hash 15dfb2762480c825beb4f3cf3c57becf9386c02065f23525604fef2c8992f280 was observed by OffSeq Mirage honeypot sensors 58 times during attacker activity between August 13 and August 14, 2026. The activity involved the MITRE ATT&CK technique T1105 (Ingress Tool Transfer). The file is associated with a malicious payload that could be a dropper, web shell, miner, or post-exploitation tool. The attacker infrastructure was observed in multiple countries including Argentina, Brazil, Chile, China, Hong Kong, Luxembourg, Pakistan, and Saudi Arabia. This indicator should be matched against files in environments and security tools to detect potential compromise.
A malicious file identified by the SHA-256 hash 5f3709aa1823bc153c63dc5d0bccab9fbf9e252a910a08a639e857bd9f8f0149 was observed by OffSeq Mirage honeypot sensors on 2026-08-08. The file is associated with attacker activity involving the MITRE ATT&CK technique T1105 (Ingress Tool Transfer) and was seen originating from attacker infrastructure in Germany. The hash corresponds to a specific malicious payload, which could be a dropper, web shell, miner, or post-exploitation tool. This indicator should be matched against files in environments and security tools to detect potential compromise.
A malicious file identified by the SHA-256 hash 135cefead339d5e0813e38049da8666efefef7c7b64c6ed22f5fec62b676ced1 was observed by OffSeq Mirage honeypot sensors on August 8, 2026. The file was detected twice during attacker activity involving the T1105 technique (Ingress Tool Transfer). The malicious payload could be a dropper, web shell, miner, or post-exploitation tool. The attacker infrastructure was located in Germany. This hash can be used as an indicator of compromise to detect the presence of this malicious file in environments and security tools.
A malicious file identified by the SHA-256 hash ca2af697388746b2381dc7c4e857ffcec86223ea4618de4583437380050d7770 was observed by OffSeq Mirage honeypot sensors on 2026-08-08. The file was involved in attacker activity using the MITRE ATT&CK technique T1105 (Ingress Tool Transfer), indicating it was used to stage or deliver a malicious payload such as a dropper, web shell, miner, or post-exploitation tool. The attacker infrastructure was located in Germany (DE). This indicator can be used to detect the presence of this malicious payload in environments by matching the hash against files in endpoint detection and response (EDR), antivirus (AV), and threat intelligence feeds.
A malicious file identified by the SHA-256 hash 41973e5dc419ef5d31ba3c0b984ae22d80dddd15d3bf65696e7e0c919134430f was observed twice in attacker activity on August 8, 2026. The activity involved the MITRE ATT&CK technique T1105 (Ingress Tool Transfer), indicating the file was used to stage or deliver a malicious payload such as a dropper, web shell, miner, or post-exploitation tool. The attacker infrastructure was located in Germany. This file hash serves as an indicator of compromise (IOC) for detection and response efforts.
A malicious file identified by the SHA-256 hash f2e2ffc024ab99eb49fa207756481aa80713398142f30888aebace5706909b36 was observed 182 times in attacker activity between August 7 and August 29, 2026. The file is associated with the ATT&CK technique T1105 (Ingress Tool Transfer) and is linked to attacker infrastructure in multiple countries including Argentina, Brazil, Canada, China, Indonesia, India, Italy, and Jordan. The hash fingerprints a specific malicious payload that could be a dropper, web shell, miner, or post-exploitation tool. This indicator should be matched against files in environments and security tools to detect potential compromise. No known exploits in the wild or vendor patches are applicable.
A malicious file identified by the SHA-256 hash 848f1546a84dd92cce3c1463e3e964698533d93d6ea7be00e000db5efbb1d2f4 was observed by OffSeq Mirage honeypot sensors eight times between August 6 and August 11, 2026. The file is associated with attacker activity involving the MITRE ATT&CK technique T1105 (Ingress Tool Transfer). The malicious payload could be a dropper, web shell, miner, or post-exploitation tool. The attacker infrastructure was observed in Chile (CL) and China (CN). There is no known exploit in the wild or vendor patch information available. Organizations are advised to match this hash against files in their environment and threat intelligence feeds.
A malicious file identified by the SHA-256 hash f2291321df3b93aed41359a2f5f3fa22bf4a16da1a13343cc3daca9657fbac6c was observed by OffSeq Mirage honeypot sensors on August 6, 2026. This file was detected six times during attacker activity involving the T1105 technique (Ingress Tool Transfer). The malicious payload could be a dropper, web shell, miner, or post-exploitation tool. The attacker infrastructure was observed in Ethiopia, India, and Turkey. There is no known exploit in the wild or vendor patch information associated with this indicator. Organizations are advised to match this hash against files in their environment and security feeds.
A malicious file identified by the SHA-256 hash e4e6d77040f6a91d42292fe7b8fbf9e6ca5722c940097e21a345d03b522af43d was observed 95 times in attacker activity between August 4 and August 11, 2026. The file is associated with the MITRE ATT&CK technique T1105 (Ingress Tool Transfer) and is linked to attacker infrastructure in multiple countries. This hash fingerprints a specific malicious payload that could be a dropper, web shell, miner, or post-exploitation tool. Organizations are advised to match this hash against files in their environments and security feeds to detect potential compromise.
A malicious file identified by the SHA-256 hash ee86d4b3017ccb464b3d27332ceed33de1a9e3836e2cf55adced642d210bef7f was observed by OffSeq Mirage honeypot sensors on 2026-08-04. The file is associated with attacker activity involving the T1105 technique (Ingress Tool Transfer) and was seen originating from attacker infrastructure in Israel. This hash fingerprints a specific malicious payload which could be a dropper, web shell, miner, or post-exploitation tool. Organizations are advised to check this hash against their environments and security tools. No known exploits or threat actors are currently linked to this indicator.
A malicious file identified by the SHA-256 hash 4af5a5c98ad132095c6fbe7b02c242153a190a01cc321e50a916a0ca46fbaa62 was observed 618 times in attacker activity between August 4 and August 11, 2026. The file is associated with the MITRE ATT&CK technique T1105 (Ingress Tool Transfer) and was seen originating from attacker infrastructure in Germany. This hash fingerprints a specific malicious payload that could be a dropper, web shell, miner, or post-exploitation tool. Organizations are advised to match this hash against files in their environments and security tools to detect potential compromise.
A malicious file identified by the SHA-256 hash cac00f4de01f0b46d9646e425ae88152df96d7393c98099f2a373e86dbd56176 was observed by OffSeq Mirage honeypot sensors 79 times between July 31, 2026, and August 5, 2026. The file is associated with attacker activity involving the MITRE ATT&CK technique T1105 (Ingress Tool Transfer). The malicious payload could be a dropper, web shell, miner, or post-exploitation tool. The attacker infrastructure was observed in multiple countries, but no specific targeted countries are confirmed. There is no known exploit in the wild or vendor patch information related to this file hash. This is an indicator of compromise (IOC) to be matched against files in environments and security tools.
A malicious file identified by the SHA-256 hash 92a919c18841e8ff2a2e1165a3d446f06fba4e866f7e6d8fd6dd4933e43985f8 was observed by OffSeq Mirage honeypot sensors on 2026-07-31. The file was detected three times during attacker activity involving the T1105 technique (Ingress Tool Transfer), indicating it was used to stage or deliver a malicious payload such as a dropper, web shell, miner, or post-exploitation tool. The attacker infrastructure was located in the United States. This indicator can be used to match against files in environments and security tools to detect potential compromise.
A malicious file identified by the SHA-256 hash ab8d6adf1976431e290cc6d5991f0e23dfc450ee89463b0bcf8191601c0cc0c4 was observed by OffSeq Mirage honeypot sensors during attacker activity between July 30 and August 1, 2026. The file is associated with the MITRE ATT&CK technique T1105 (Ingress Tool Transfer) and was seen originating from attacker infrastructure in Germany. This hash fingerprints a specific malicious payload that could be a dropper, web shell, miner, or post-exploitation tool. Organizations are advised to match this hash against files in their environments and security telemetry to detect potential compromise.
A malicious file identified by the SHA-256 hash 8f312413d911af37f7636c63f33fb48b5f6d15c68a04a3db42a3189e24690d3f was observed by OffSeq Mirage honeypot sensors four times between July 30 and August 1, 2026. The file is associated with attacker activity involving the MITRE ATT&CK technique T1105 (Ingress Tool Transfer). The malicious payload could be a dropper, web shell, miner, or post-exploitation tool. The attacker infrastructure was located in Germany and Great Britain. This indicator can be used to detect or block the malicious file in environments and security tools.
A malicious file identified by the SHA-256 hash 41f06f992406b144eaa87a5a91961a8ab4e46d9a38fc94e03ccd644a97252949 was observed by OffSeq Mirage honeypot sensors five times between July 29, 2026, and August 2, 2026. The file is associated with attacker activity involving the MITRE ATT&CK technique T1105 (Ingress Tool Transfer). The malicious payload could be a dropper, web shell, miner, or post-exploitation tool. The attacker infrastructure was located in the Netherlands. This indicator can be used to detect the presence of this specific malicious file in environments and security tools.
The OffSeq Mirage honeypot sensors detected a malicious file identified by the SHA-256 hash bf20fa97c5afa6cb4d25611fb5a6b9d1fc3dc18ecb07f6ba1bd80d9de05ad5b2. This file was observed twice on July 28, 2026, associated with attacker activity involving the T1105 technique (Ingress Tool Transfer). The hash corresponds to a specific malicious payload, which could be a dropper, web shell, miner, or post-exploitation tool. The file was seen originating from attacker infrastructure located in MU. There is no indication of known exploits in the wild or specific affected software versions. No patch or remediation information is available.
A malicious file identified by the SHA-256 hash 5f0f014674efd7ae577b0cce3b2a056dcae394d81c5ab5c09b311cf5f2fbb83c was observed by OffSeq Mirage honeypot sensors on 2026-07-28. The file is associated with attacker activity involving the T1105 technique (Ingress Tool Transfer), indicating it was used to stage or deliver a malicious payload such as a dropper, web shell, miner, or post-exploitation tool. This indicator is intended for matching against files in environments and security feeds to detect potential compromise. No known exploits in the wild or specific affected software versions are identified.
A malicious file identified by the SHA-256 hash d487a3bbd941c891d83433d955b05d9a569a04a61f8dc6b33b79c8842dc42100 was observed by OffSeq Mirage honeypot sensors on 2026-07-28. The file is associated with attacker activity involving the MITRE ATT&CK technique T1105 (Ingress Tool Transfer), indicating it was used to stage or deliver a malicious payload such as a dropper, web shell, miner, or post-exploitation tool. The file was seen originating from attacker infrastructure located in MU. There is no indication of known exploits in the wild or specific affected software versions. This indicator should be matched against files in environments and security tools to detect potential compromise.
A malicious file identified by the SHA-256 hash 87da5dd36a95e1c0acbaff137a56d94a9339fdcf42577974b53fbd6f69c11219 was observed twice on July 28, 2026, by OffSeq Mirage honeypot sensors. The activity involved the ATT&CK technique T1105 (Ingress Tool Transfer), indicating the file was transferred from attacker infrastructure located in MU. The file is associated with malicious payloads such as droppers, web shells, miners, or post-exploitation tools. No specific software versions or exploits in the wild are reported. This indicator should be matched against files in environments and security tools to detect potential compromise.