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.
BRIEFR is a self-hosted, open-source tool designed to provide CVE and IOC intelligence as part of a modular SIEM approach. It aggregates data from multiple threat intelligence sources such as NVD, CISA KEV, FIRST EPSS, and various exploit feeds, scoring CVEs against a user's technology stack. The tool also supports IOC lookups via free-tier VirusTotal, AbuseIPDB, MalwareBazzar, and URLHaus, and integrates Sigma community rules and SIEM query starters tied to ATT&CK. BRIEFR is currently in early alpha, intended for personal use with no major issues reported, and is not a vulnerability or threat itself. It is a security tool aimed at improving threat intelligence and situational awareness.
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.
A malicious file identified by the SHA-256 hash a330fdc4266c2163a661aab758c06d52de0e923872dfb95f16f371183d4280f0 was observed by OffSeq Mirage honeypot sensors on 2026-07-28. The file was detected twice in attacker activity involving the T1105 technique (Ingress Tool Transfer) originating from attacker infrastructure in MU. This hash corresponds to a malicious payload such as a dropper, web shell, miner, or post-exploitation tool. Organizations are advised to check their environments and security tools for this file hash to detect potential compromise.
A malicious file identified by the SHA-256 hash 6da698e64fba6eceba3457ffe1b5f844c8f155f46825da36ed67b4db66ef12af was observed by OffSeq Mirage honeypot sensors three times between July 27 and July 31, 2026. The file is associated with attacker activity involving the MITRE ATT&CK technique T1105 (Ingress Tool Transfer). The malicious payload may be a dropper, web shell, miner, or post-exploitation tool. The file was seen originating from attacker infrastructure in Bulgaria. 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 b9b0d9654fea3fd034fa62ae3d8805379c8c7fe5168b7c44f2f55702e541e72e was observed by OffSeq Mirage honeypot sensors on July 27, 2026. The file was detected twice in 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 MU. This indicator can be used to detect the presence of this specific 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 da6d923c304f3844fb563ec63a9ff3b62f5cc177335192dfbc55667d24d9308d was observed by OffSeq Mirage honeypot sensors on 2026-07-26. The file is associated with attacker activity involving the MITRE ATT&CK technique T1105 (Ingress Tool Transfer). This hash fingerprints a specific malicious payload that could be a dropper, web shell, miner, or post-exploitation tool. The activity was observed from attacker infrastructure located in MU. Organizations are advised to check this hash against their environments and security tools to detect potential compromise.
A malicious file identified by the SHA-256 hash 805a01d5cda9cf31423b7fc2cc70165098505500c9107bb47b4303c0a60cb208 was observed twice on July 26, 2026, by OffSeq Mirage honeypot sensors. 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. This indicator can be used to detect the presence of this specific 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 0cb070e16ed2c0c6b1df1df4ffa57be59c4bed42f8ac3803d37d0c54c7c9f958 was observed twice in attacker activity on July 26, 2026. The file is associated with 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 activity was detected by OffSeq Mirage honeypot sensors and linked to attacker infrastructure in MU. There is no information on known exploits in the wild or affected software versions.
A malicious file identified by the SHA-256 hash dc8586402cbd86a2593fab196f3ced051326c21120144264492c07c5d91f2cfa was observed by OffSeq Mirage honeypot sensors on 2026-07-26. The file was detected twice in attacker activity involving the T1105 technique (Ingress Tool Transfer). This hash corresponds to a specific malicious payload such as a dropper, web shell, miner, or post-exploitation tool. The attacker infrastructure was located in Bulgaria (BG).