A malicious file identified by the SHA-256 hash 1c0688bb8702fd6c977efffa5e9d1a5c2da77431d41bd6c31f86cbc3ce368700 was observed by OffSeq Mirage honeypot sensors on 2026-10-24. The file was detected four times in attacker activity involving the T1105 technique (Ingress Tool Transfer) originating from attacker infrastructure in Poland. This hash corresponds to a specific malicious payload such as a dropper, web shell, miner, or post-exploitation tool. No known exploits or threat actors have been associated with this indicator yet. There is no information about affected software versions or patches.
A malicious file identified by the SHA-256 hash d53eda7a637c99cc7fb566d96e9fa109bf15c478410a3f5eb4d4c4e26cd081f6 was observed by OffSeq Mirage honeypot sensors on 2026-10-24. The file is associated with attacker activity involving the MITRE ATT&CK technique T1105 (Ingress Tool Transfer). The payload could be a dropper, web shell, miner, or post-exploitation tool. The file was seen originating from attacker infrastructure in Poland. There is no information about active exploitation or affected software versions. This indicator should be matched against files in environments and security tools for detection purposes.
The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security Fix(es):
* kernel: tcp: restrict SO_ATTACH_FILTER to priv users (CVE-2026-53236)
* kernel: fuse: re-lock request before replacing page cache folio (CVE-2026-53388)
* kernel: writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs() (CVE-2026-64378)
* kernel: net: gro: fix double aggregation of flush-marked skbs (CVE-2026-68136)
* kernel: net/packet: avoid fanout hook re-registration after unregister (CVE-2026-68338)
* kernel: net/iucv: fix use-after-free of a severed iucv_path (CVE-2026-68140)
* kernel: net/sched: serialize qdisc_rtab_list against concurrent get/put (CVE-2026-68138)
* kernel: ipvs: reload ip header after head reallocation (CVE-2026-68476)
* kernel: mptcp: options: reset DSS fields in case of unexpected size (CVE-2026-80586)
* kernel: usb: usbfs: fix use-after-free of usb_device in usbdev_release() (CVE-2026-80824)
* kernel: smb: client: clear setuid/setgid bit on write with cifsacl/modefromsid/posix extensions (CVE-2026-89638)
* kernel: net/iucv: filter frames in afiucv_hs_rcv() by ingress device (CVE-2026-81003)
* kernel: ipv4: validate checksum_start before completing checksum
(CVE-2026-99999)
Bug Fix(es) and Enhancement(s):
* Backport 6785011f8b16 ("ipv4: validate checksum_start before completing checksum") [rhel-8.10.z] (JIRA:RHEL-280584)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
The URL http://play.nopixel-rp.ir/ was observed twice in attacker activity on 2026-10-24 by OffSeq Mirage honeypot sensors. It is associated with the MITRE ATT&CK technique T1105 (Ingress Tool Transfer), indicating its use in attacker payloads such as tool downloads, callbacks, or exploitation targets. The attacker infrastructure was identified as originating from Great Britain. This URL serves as an indicator of compromise (IOC) and should be blocked and monitored in network defenses.
Python 2.7's ssl module has been updated to include a denylist of known compromised certificates. This denylist ensures that such certificates are automatically rejected even if certificate revocation checking is not configured. The update enhances user safety by preventing the acceptance of compromised certificates regardless of SSLContext policy settings.
An attacker URL https://wrpddqm0rp.rbmock.dev/ was observed in the wild by OffSeq Mirage honeypot sensors on 2026-10-24. The URL was seen 4 times in attacker activity related to the T1105 technique (Ingress Tool Transfer), indicating its use for payload delivery or command and control. The attacker infrastructure was located in Colorado, USA. This URL is associated with attacker payloads such as tool downloads, callbacks, or exploitation targets. No specific software versions are affected, and no known exploits are reported in the wild for this indicator.
open62541 versions before 1.5.7 contain an integer overflow vulnerability in the UA_DataType_fromStructureDescription() function. This overflow occurs due to wrapping of the 16-bit memSize field when processing large custom structure definitions supplied by a malicious OPC UA server. Exploitation can cause heap overflow, leading to client crashes or potential code execution.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Bold Grid W3 Total Cache w3-total-cache allows Stored XSS.This issue affects W3 Total Cache: from n/a through 2.10.7.
A malicious file identified by the SHA-256 hash b5149190ab5cdfcee95c4aa201bdd0229f426d3bbf6d2cd45d0e983f120b94b7 was observed by OffSeq Mirage honeypot sensors on 2026-10-24. This file was seen 9 times 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. No specific software versions or products are affected, and no known exploits in the wild have been reported. The file hash serves as an indicator of compromise (IOC) for detection and response purposes.
A malicious file identified by the SHA-256 hash d5d4249912afc83472420ec77c8a97081800436df1e31d14bb814649e084e061 was observed by OffSeq Mirage honeypot sensors on 2026-10-24. This file was detected 9 times 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 threat is an indicator of compromise (IOC) rather than a vulnerability or exploit itself. No known exploits or threat actors are associated with this hash, and no affected software versions or countries are specified.
The OffSeq Mirage honeypot sensors detected a malicious file identified by the SHA-256 hash ef251d66663f4a97882fcdcf7622a377c2b3068c26763f73e1ec0a81136342dc. This file was observed 10 times on October 24, 2026, associated with attacker activity using the MITRE ATT&CK technique T1105 (Ingress Tool Transfer). The hash corresponds to a malicious payload that could be a dropper, web shell, miner, or post-exploitation tool. No specific software versions or products are affected, and no known exploits in the wild have been reported. The threat is an indicator of compromise (IOC) useful for detection and response efforts.
A malicious file identified by the SHA-256 hash 31087290fc269af7921f9591418ac5d0baff3304bc3a18bc7b614546766586e9 was observed by OffSeq Mirage honeypot sensors on 2026-10-24. This file was detected 9 times 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. There is no information on affected software versions or known exploits in the wild. The file hash serves as an indicator of compromise (IOC) to be matched against files in environments and security tools.
A malicious file identified by the SHA-256 hash 792a633371540ee9695ed6923f566de4a41cdaec6883e5b537d8ef848ee8636e was observed by OffSeq Mirage honeypot sensors on 2026-10-24. This file was detected 9 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. No specific software versions or geographic targeting are indicated. No known exploits in the wild or threat actors are associated with this indicator at this time.
A malicious file identified by the SHA-256 hash 0616c20dea0ff2bd59fff5b60b3e907231d8c99296d0a0c719ba553f83dbd056 was observed 10 times on 2026-10-24 by OffSeq Mirage honeypot sensors. 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. No direct exploit or patch information is provided.
A malicious file identified by the SHA-256 hash 9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08 was observed 9 times on 2026-10-24 by OffSeq Mirage honeypot sensors. The file is associated with attacker activity involving the MITRE ATT&CK technique T1105 (Ingress Tool Transfer). This hash fingerprints a specific malicious payload which could be a dropper, web shell, miner, or post-exploitation tool. Organizations should match this hash against files in their environments and threat intelligence feeds to detect potential compromise.
@sxm-web/client-sdk-core is a dependency-confusion package: it is described as a "Compatibility shim", uses inflated version numbers, and its README calls it an "authorized dependency-confusion test". Each listed version (0.0.1, 1.0.0, 1.0.1, 2.0.0, 1.1.0, 3.0.0, 13.3.7) has a postinstall script that runs `node beacon.cjs` on npm install, and index.js calls the same code when the package is imported; it POSTs the hostname, install path and current working directory over plain HTTP to `http://185.158.107.175:8787/_ah/dc`, and index.js exports a Proxy that returns no-op functions so builds importing the real package keep running. The npm account wiseke published 14 such packages under the @greenlake, @sxm-web, @drone-js-ext and @ppa-web-components scopes between 2026-10-23 21:23 and 2026-10-25 14:28 UTC; index.js is byte-identical to that of ph-common (MAL-2026-1809), which sends to the same endpoint.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (8d53280e50e3f0ad06e3ab6e3685856cd774465fd6d4461d64e22caad4ee94fc)
@sxm-web/client-sdk-core@1.0.1 is a stub package whose only functional code is a beacon. The declared postinstall script runs `node beacon.cjs`, and the same beacon is also invoked at require time from index.js. The beacon collects installer-side identifiers (hostname, install path, current working directory, Node.js version, package name) and POSTs them in cleartext over plain HTTP to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc, which is unrelated to any legitimate registry or publisher infrastructure. The package's `main` returns a Proxy that produces no-op functions for every accessed property, so the package provides no advertised functionality — the install itself is the payload. The scoped name `@sxm-web/client-sdk-core` combined with a `Compatibility shim` description is consistent with a dependency-confusion probe aimed at an internal/private SDK namespace, where the beacon's purpose is to confirm successful resolution against private names and to disclose the resolving host's identity and filesystem layout to the operator at the bare IP.
## Source: ghsa-malware (8a5670fe68642a259935664dbac1c7c569c1af0b09253570a72909b92c7ac1c5)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
A critical vulnerability exists in the Cranelift compiler backend of Wasmtime on aarch64 architectures prior to versions 36.0.19, 48.0.7, and 49.0.4. The flaw allows a Wasm br_table instruction with more than approximately 256,000 targets to compile incorrectly, resulting in a conditional branch that can jump to arbitrary code. This enables a user-controlled WebAssembly module to escape the sandbox, potentially leading to full compromise on affected systems. The issue is fixed in the specified versions.