termination

Winsage
September 23, 2026
Security researcher Abdelhamid Naceri, known as Nightmare Eclipse, released a zero-day exploit called BigDiskBuster that targets Microsoft Defender, preventing antivirus updates and leaving systems vulnerable. BigDiskBuster operates across all supported Windows versions and must run in the background to block updates. Naceri has previously released a similar exploit called UnDefend and has a history of releasing multiple zero-day exploits since April 2026 amid a dispute with Microsoft. Two weeks before BigDiskBuster, he introduced another exploit named ShieldCrash, which grants SYSTEM access and circumvents a patched flaw. Naceri's recent exploits include tools like LegacyHive, BlueHammer, RedSun, YellowKey, GreenPlasma, and MiniPlasma, all targeting Microsoft Defender and other Windows components. Microsoft has warned of potential legal action against malicious activities but has not commented on BigDiskBuster.
AppWizard
September 21, 2026
In August 2026, Google Play announced new performance requirements for memory management that will be enforced starting February 2027. These requirements include metrics for dynamic memory usage, bitmap memory, and DEX code optimization. Applications that exceed these thresholds may face reduced visibility and publishing capabilities on the platform. Dynamic memory usage is defined as the sum of anonymous RSS and swap, excluding file-backed data. Google is focused on whether applications retain non-visible bitmaps and requires at least 25% coverage in DEX optimization. Memory issues can be difficult to reproduce, and developers are encouraged to use Android Studio’s Memory Profiler to investigate memory growth. A thorough investigation involves monitoring memory changes, taking heap dumps, and understanding reference paths. Bitmap memory should be carefully managed, as the runtime cost of images can exceed their file size. Google will provide real-world memory metrics through the Play Console, and teams are advised to establish memory budgets and perform pre-release checks to identify potential issues before they lead to out-of-memory (OOM) crashes.
Winsage
September 15, 2026
Microsoft announced on September 14 that the Windows 11 24H2 edition, including Home and Pro versions, has only 30 days of support remaining, with a deadline for updates set for October 13, 2026. Users are encouraged to upgrade to version 25H2 or later to continue receiving security updates. The Enterprise and Education editions will have support until October 12, 2027. Users have reported issues from September's security updates, particularly with the Office patch KB5002914, which disrupts the copy-and-paste function in Excel across multiple versions. Microsoft has acknowledged the issue but has not yet released a fix. A temporary workaround involves manually removing the problematic patch, though this also removes the associated security fixes. Additionally, users have experienced connection drops and unresponsiveness in Remote Desktop Services (RDS) across various Windows versions, including Windows 11 26H1 and Windows Server 2012. Microsoft confirmed that related tools may also stop responding, and restarting virtual machines may temporarily restore functionality. USB audio issues have been reported on certain USB Audio Class 1.0 devices across Windows 11 versions, with users experiencing loss of audio output and corrupted sound settings. Switching to 2-channel mode has helped some users, but Microsoft has not provided a timeline for a comprehensive fix. As Windows Server 2012 nears the end of its Extended Security Updates period on October 13, 2026, the RDS issues add pressure on administrators. Users on 24H2 need to prioritize migration to 25H2, while those with the latest updates should be cautious regarding Excel and Remote Desktop functionalities.
Winsage
September 2, 2026
An active malware campaign is using counterfeit software-download websites to distribute malicious installers, primarily targeting users seeking popular software. This campaign has significantly affected China-based operations of multinational corporations and Chinese-speaking users. The malware, once executed, can establish persistence, undermine security measures, and communicate with attacker-controlled infrastructure. Victims span various sectors, including healthcare, manufacturing, gaming, technology, logistics, government, and education. Microsoft associates this campaign with a Chinese threat cluster called Silver Fox, known for using spoofed vendor download pages to spread Gh0st RAT and ValleyRAT. The malicious websites are hosted on .com.cn and .hl.cn domains, featuring Chinese-language content. The downloaded files are dynamically generated, and upon execution, they deploy a wrapper installer that initiates the malware payload. The malware achieves persistence through scheduled tasks and interferes with Windows Update services. The campaign establishes command-and-control communication over non-standard ports, with two identified domains linked to the activity. Microsoft Defender has detected the threat and initiated containment procedures. Kaspersky reported a related malicious installer exploiting a legitimate adware application to execute a backdoor, which captures keystrokes and clipboard contents. ValleyRAT, a sophisticated implant, can collect system information, reboot the computer, capture screenshots, and transmit logs. The attackers are motivated by cyber espionage and financial gain, targeting organizations globally. A subgroup within GoldenEyeDog, known as CuboidalCanine, has also been linked to the use of ValleyRAT, particularly in the gambling industry. In June 2026, Chinese authorities addressed cybercrime cases involving a new variant of the Silver Fox trojan.
Tech Optimizer
September 1, 2026
Choosing a database instance size without prior knowledge of the workload can lead to inefficiencies and excessive compute usage. Lakebase Postgres addresses this with an autoscaling feature that eliminates manual sizing, utilizing in-place VM resizing and a monitoring algorithm for CPU, memory, and working set size. Lakebase Postgres separates compute and storage layers, allowing independent resizing of compute nodes without affecting the database. The autoscaling algorithm relies on three signals: CPU load (cpuGoalCU), memory use (memGoalCU), and compute-cache working set size (lfcGoalCU). The CPU load is monitored every five seconds, aiming to maintain it at or below 90% capacity. Memory usage is tracked at two frequencies: overall memory every five seconds and Postgres-specific memory every 100 milliseconds, with a goal to keep usage below 75% of allocated RAM. The compute cache evaluates active data access efficiency, adjusting size based on workload. The working set is estimated using a modified HyperLogLog algorithm that records timestamps for page accesses, allowing for distinct page estimates over various time frames. The algorithm projects future working-set growth to allocate sufficient cache while capping it at 75% of RAM. Resizing the compute involves four components: the autoscaler-agent, vm-monitor, Kubernetes scheduler, and NeonVM. Scaling up occurs when any of the three goals indicate a need for more resources, while scaling down includes verification to ensure sufficient memory remains for operations. Timely adjustments in both directions are prioritized to minimize costs.
AppWizard
August 27, 2026
Google has announced new memory-usage restrictions for Android applications to address the ongoing RAM crisis. These restrictions require developers to comply with new memory constraints to ensure smoother operation across devices. The initiative coincides with the rollout of Android 17, which is being introduced on devices like the Pixel 11 Pro and 11 Pro XL, both of which have less RAM than previous models. Developers must consider varying RAM configurations, ranging from 4GB to over 16GB. Applications that exceed the memory limits may experience reduced performance, slowdowns, or termination, and may face diminished visibility on the Google Play Store. These memory limits will take effect in February 2027, providing developers time to adjust their applications.
AppWizard
August 27, 2026
Starting in early 2027, Android apps on Google Play must meet new memory performance standards due to rising RAM prices and consumer demand for streamlined smartphones. Google is concerned about a potential "ecosystem-wide memory crisis" and aims to improve memory efficiency in app development. The new standards will be implemented in two phases: the first phase in February 2027 will set thresholds for undesirable behavior and code optimization, while the second phase in April 2027 will enhance device migration with a zero-tap credential restoration feature. Specific memory limits include: - For devices with 8 GB of RAM: foreground app usage capped at 2.25 GB, 1.5 GB for user-perceived services, and 1.5 GB for background processes. - Devices with more than 16 GB of RAM will be largely exempt from these restrictions. - Bitmap memory usage limited to 200 MB for user-perceived and background services, with a cached limit of 400 MB across all devices. - Gaming applications will have different memory requirements. The DEX code optimization mandate aims to improve memory utilization, app launch speed, and runtime performance. The zero-tap sign-in requirement in the second phase seeks to streamline device migration and enhance security, addressing risks associated with manual sign-ins.
AppWizard
August 27, 2026
Google is implementing stricter oversight on RAM usage by applications and games to enhance the performance of Android devices. New memory usage restrictions will be introduced on Google Play, requiring apps to adhere to specified memory thresholds, with potential consequences for non-compliance, including slowdowns, termination by the system, reduced visibility in the Google Play store, and publishing restrictions. Monitoring of compliance will begin in February 2027, following the introduction of memory limits with Android 17 on Pixel smartphones. This initiative is linked to a RAM shortage affecting the device market, with reports indicating that the base versions of the Pixel 11 Pro and Pixel 11 Pro XL have less RAM than their predecessors.
Search