A malicious file identified by the SHA-256 hash 3674a103804cac96027fe1cf62aaab4948c1d547d1c885542177a263103b4260 was observed by OffSeq Mirage honeypot sensors during attacker activity between November 14 and November 19, 2026. The file is associated with the ATT&CK technique T1105 (Ingress Tool Transfer) and may represent 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.
This entry references internally found bugs fixed in Firefox ESR 140.14, Firefox ESR 153.1, and Firefox 154, but the provided data pertains to a Microsoft vulnerability (CVE-2026-74987) with minimal details. The description does not detail the nature of the vulnerability or its impact. No patch or remediation information is provided.
A use-after-free vulnerability exists in the Disability Access APIs component of Microsoft software version 4.0, which could allow a sandbox escape. This vulnerability was published on November 14, 2026. No CVSS score or detailed impact metrics are provided, and there is no information about active exploitation or available patches.
A use-after-free vulnerability exists in the JavaScript WebAssembly component of Microsoft software version 4.0. This flaw is identified as CWE-416 and was published on November 14, 2026. No CVSS score or detailed impact information is provided, and no known exploits are reported in the wild. No patch or remediation details are available from the vendor at this time.
An uninitialized memory vulnerability exists in the Audio/Video: Web Codecs component of Microsoft software version 4.0. The issue was publicly disclosed on November 14, 2026. No CVSS score or detailed impact information is provided, and there are no known exploits in the wild. No patch or remediation details are available in the provided data.
This entry references internally found bugs fixed in various Firefox ESR versions and Firefox 154, but the provided data relates to a Microsoft vulnerability (CVE-2026-74990) with minimal details. The description does not specify the nature of the vulnerability or its impact. No patch information or remediation details are provided.
The HashiCorp cap JWT validation library versions before 0.14.0 contain a vulnerability that allows bypassing claims validation. This flaw may cause downstream applications to make authorization decisions based on unvalidated claim values. The vulnerability requires attacker-controlled claims in a JWT signed by a trusted key. It is fixed in version 0.14.0.
A malicious file identified by the SHA-256 hash 8287d65844b6b116dbd3ec838c362577aa33257c192eb8c1107bb190b1668d36 was observed by OffSeq Mirage honeypot sensors on 2026-11-14. This file was detected seven times in attacker activity involving the T1105 technique (Ingress Tool Transfer) originating from attacker infrastructure in the Netherlands. The file is associated with a malicious payload such as a dropper, web shell, miner, or post-exploitation tool. 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 ad4ec186ede7f4e22525b1f0d7657a96aa5397f5cb9ea2510ba55677437e8b64 was observed by OffSeq Mirage honeypot sensors on 2026-11-14. This file was seen three times in attacker activity involving the T1105 technique (Ingress Tool Transfer) originating from attacker infrastructure in the Netherlands. The file is associated with a malicious payload such as a dropper, web shell, miner, or post-exploitation tool. Organizations are advised to check for this hash in their environments and security tools.
A malicious file identified by the SHA-256 hash 7905c4ad4267729450a64aee8807b347ba1eb09d35d70afa3b0488ecab2de831 was observed by OffSeq Mirage honeypot sensors on 2026-11-14. The file was detected seven times during attacker activity involving the T1105 technique (Ingress Tool Transfer) from infrastructure located in the Netherlands. This hash corresponds to 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 to detect potential compromise.
A malicious file identified by the SHA-256 hash 08bad1503658a73333a903e2aa8dc28a4f7cddc8eaa6779d2f16ac40128ec8b7 was observed three times on November 14, 2026, by OffSeq Mirage honeypot sensors. 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 delivered or staged during the attack. The attacker infrastructure was located in the Netherlands. This indicator can be used to detect and block the malicious file in affected environments.
A malicious file identified by the SHA-256 hash 6b06d98a817f5f25009af8fdef6a077a750259519fbac9b02176dcf497be0a8e was observed by OffSeq Mirage honeypot sensors on 2026-11-14. This file was detected seven times during attacker activity involving the T1105 technique (Ingress Tool Transfer) originating from attacker infrastructure in the Netherlands. The file hash corresponds to a malicious payload that could be a dropper, web shell, miner, or post-exploitation tool. Organizations are advised to check their environments and security tools for this hash to detect potential compromise.
A malicious file identified by the SHA-256 hash e1e275cf672d481750730a3b46b1d1683ae030573533d3feed87f4e63196a9ac was observed by OffSeq Mirage honeypot sensors on 2026-11-14. The file was detected three times during attacker activity involving the T1105 technique (Ingress Tool Transfer) originating from attacker infrastructure in the Netherlands. This hash corresponds to a specific 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 hash to identify potential compromise.
A malicious file identified by the SHA-256 hash 6fbdd13040b4716599a1dca4797b1fbe9b1d1df002ed4ef67147462dd288a39e was observed by OffSeq Mirage honeypot sensors on 2026-11-14. This file was detected seven times during attacker activity involving the T1105 technique (Ingress Tool Transfer) from attacker infrastructure located in the Netherlands. The file is associated with a malicious payload such as 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 identify potential compromise.
A malicious file identified by the SHA-256 hash af3e4ef0c18704fc45dc2276cae6d0010449778066c67c93c1891f62fcd3a54d was observed by OffSeq Mirage honeypot sensors on 2026-11-14. This file was detected three times during attacker activity involving the T1105 technique (Ingress Tool Transfer) from attacker infrastructure located in the Netherlands. The hash corresponds to a 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.
NLTK versions prior to 3.10.4 contain a vulnerability in the dependency graph image rendering function where the Graphviz dot executable is resolved and invoked insecurely. This allows a local low-privileged attacker with write access to a directory in the victim's PATH to execute arbitrary code by planting a malicious dot executable. The issue is fixed in version 3.10.4.
A vulnerability in dbus configured with the nonce-tcp transport allows an unauthenticated attacker to cause a denial of service by opening a connection and withholding the authentication token. This stalls the server's accept process, blocking legitimate clients from connecting. The issue arises because the server does not enforce a timeout during authentication verification. Default installations are not affected as they use local UNIX domain sockets. Mitigation involves disabling nonce-tcp listeners or restricting access via firewall rules.
A malicious file identified by the SHA-256 hash ed968e840d10d2d313a870bc131a4e2c311d7ad09bdf32b3418147221f51a6e2 was observed by OffSeq Mirage honeypot sensors during attacker activity between November 13 and 14, 2026. The file is associated with the ATT&CK technique T1105 (Ingress Tool Transfer) and was seen originating from attacker infrastructure in Brazil. This hash corresponds to a specific malicious payload such as a dropper, web shell, miner, or post-exploitation tool that was staged or delivered during the attack. Organizations are advised to match this hash against files in their environments and security feeds to detect potential compromise.
Vault's Login MFA feature had a vulnerability where it did not consistently enforce expiration of pending two-phase login requests. This flaw could allow a user who completed the first authentication factor to finalize MFA and obtain a Vault token after the request should have expired, even if the user's primary credential was rotated. The issue is fixed in Vault Community Edition 2.2.2 and Vault Enterprise versions 2.2.2, 1.21.14, and 1.19.26.
Vault Community Edition and Vault Enterprise versions prior to 2.2.2, 1.21.14, and 1.19.25 did not correctly apply explicit ACL deny rules to letter case variants of user and group names in certain authentication methods. This flaw could allow an authenticated user with delegated permissions to modify protected users or groups, potentially leading to privilege escalation. The issue has been fixed in the specified patched versions.