The npm package mnmobicom version 1.0.0 is identified as malicious. Although static and behavioral scans found no harmful code or suspicious activity within the package itself, the presence of this package on a system indicates a full compromise. Systems with this package installed should be considered fully controlled by an attacker, necessitating immediate secret and key rotation from a secure environment. Removing the package alone may not eliminate the compromise due to potential additional malicious software installed.
CVE-2026-68348 is a high-severity vulnerability in the Linux kernel's ASoC driver for the TAS2781 audio codec. The flaw involves improper parsing of variable-length firmware description strings, where the parser uses strlen() without ensuring the presence of a string terminator within the firmware buffer. This can cause the parser to read beyond the firmware buffer's end if the firmware image lacks a NUL terminator, potentially leading to memory access violations. The issue has been fixed by introducing a bounded string-length helper function and maintaining existing size checks.
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.
The svelte-cache-kit npm package version 1.0.0 contains malicious code that can fully compromise any computer on which it is installed or running. The package does not exhibit suspicious behavior during install or import, but its presence indicates a severe security risk. Systems with this package should be considered fully compromised, and all stored secrets and keys must be rotated from a separate, secure machine. Removing the package alone does not guarantee removal of all malicious software introduced by it.
A vulnerability was found in the golang.org/x/crypto/ssh package used by the Red Hat Trusted Artifact Signer (RHTAS) Policy Controller Operator. The Verify() method for FIDO/U2F security keys did not properly enforce user presence, allowing signatures to be accepted without requiring a physical touch on the hardware security key. This flaw could enable an attacker to use a hardware security key without user interaction, bypassing a critical security control. The issue affects the RHTAS Policy Controller Operator used with OpenShift Container Platform versions 4.16 through 4.22. No fix has been released yet.
As organizations adopt AI, they must secure both cloud and AI environments through a unified security control plane as their attack surface expands. Because modern applications and AI workloads are built and run in the cloud, security teams must understand which exposures matter most, prioritize what can truly be exploited, and reduce risk across cloud infrastructure, applications, identities, data, and AI systems in one place. Modern IT estates now span multiple clouds and on-premises systems, with architectures built on containers, Kubernetes, serverless functions, microservices, APIs, and AI-powered workloads. This increases both the volume and the interconnectedness of security signals. The challenge is no longer identifying individual risks, but determining how misconfigurations, identities, and data exposures combine to create real attack paths, and which of these are most critical to fix at the source. KuppingerCole’s Leadership Compass: Cloud Native Application Protection Platforms (CNAPP) reflects this shift. The report describes how CNAPP is evolving from a consolidation of cloud security tools into the security foundation for AI-native enterprises, combining cloud security, AI security posture management, runtime protection, attack path analysis, cloud detection and response, and agentic AI operations into unified platforms. Read the full report Within this evolving market, KuppingerCole names Microsoft a Leader across all four of its Leadership categories: Overall, Product, Innovation, and Market. In the report’s words: “Microsoft earns its Overall Leadership with its Defender for Cloud that is redefining the CNAPP market by extending cloud security beyond infrastructure protection and into a unified security platform for cloud, data, identity, AI, and security operations, supported by one of the industry’s most advanced agentic AI ecosystems.” That recognition reflects where the category is heading: toward platforms that unify cloud and AI security into one operational view of risk. Why CNAPP is being redefined KuppingerCole makes a clear point: CNAPP is no longer about posture or visibility alone. It is becoming the operational foundation for securing AI-powered applications, services, and business processes, across the full software lifecycle from cloud infrastructure to the AI systems running on top of it. Modern environments introduce complexity across: Multicloud and hybrid infrastructure. Rapid development and continuous deployment. Containers, serverless, microservices, and APIs. AI models, agents, pipelines, and machine identities. This complexity exposes the limits of traditional, siloed tools, where cloud posture, workload protection, AI security, and the security operations center (SOC) each live in their own console. Organizations now need platforms that can: Correlate posture, runtime, identity, data, application, and AI signals. Prioritize risk based on exploitability, not severity alone. Integrate security across development, cloud operations, and the SOC. Bring AI systems into the same risk model as the rest of the cloud. Runtime intelligence is now central to this shift. Across the platforms KuppingerCole evaluated, 94% detect active exploitation of the complex attack paths they surface, moving teams from long lists of findings to the exposures threat actors can actually use. What distinguishes leading platforms KuppingerCole evaluates providers on product strength, innovation, and market presence, and, more importantly, on how effectively they help organizations manage real risk across cloud and AI. Several themes define the next generation of platforms: AI security posture management that governs models, pipelines, and AI-specific attack paths. Agentic AI that investigates, validates exposures, and helps remediate, not just detect. Runtime-driven risk prioritization focused on what is exploitable in production. Security graphs and attack path analysis across identity, data, network, workload, an…
A NULL pointer dereference vulnerability exists in the Linux kernel's MPLS implementation when built with CONFIG_INET disabled. The function mpls_valid_fib_dump_req() improperly accesses a netlink attribute without checking its presence, leading to a kernel crash triggered by an unprivileged user sending a specific RTM_GETROUTE netlink message.
A Server-Side Request Forgery (SSRF) bypass vulnerability exists in stunnel versions 5.79 and lower when configured in SOCKS proxy mode. This flaw allows clients to bypass localhost restrictions by using IPv4-mapped IPv6 addresses or unspecified addresses, enabling access to loopback-only services on the stunnel host that should not be network-reachable. Exploitation requires the presence of local services bound to localhost and access to the SOCKS proxy. The vulnerability has a medium severity with a CVSS score of 5.4.
The npm package @global-theme/context version 99.9.1 contains malicious code that compromises any computer on which it is installed or running. The presence of this package indicates a full compromise of the affected system, requiring immediate rotation of all secrets and keys from a separate, uncompromised device. Removing the package alone does not guarantee eradication of all malicious software introduced by it.
The soccketio npm package version 1.0.1 contains malicious code that compromises any computer on which it is installed or running. The presence of this package indicates a full system compromise, and all secrets and keys stored on the affected machine should be rotated immediately from a different, trusted device. Removing the package alone does not guarantee removal of all malicious software introduced by it.
The npm package ethers.jsonn version 6.15.0 contains malicious code that compromises any computer on which it is installed or running. The presence of this package indicates a full system compromise, and all secrets and keys stored on the affected machine should be rotated immediately from a different, secure computer. Removing the package alone does not guarantee removal of all malicious software introduced by it.
The spectral-corsair npm package contains malicious code that compromises any computer on which it is installed or running. The presence of this package indicates a full system compromise, and all secrets and keys stored on the affected machine should be rotated immediately from a different, secure device. Removing the package alone does not guarantee removal of all malicious software introduced by it.
The npm package @patternfly-4/quickstarts version 9.9.9 contains malicious code that compromises any computer on which it is installed or running. The presence of this package indicates a full system compromise, requiring immediate removal of the package and rotation of all secrets and keys from a separate, uncompromised device. Removal of the package alone may not eliminate all malicious software introduced by its installation.