Search/Fresh WordPress Vulnerability in Attackers’ Crosshairs
● Story

Fresh WordPress Vulnerability in Attackers’ Crosshairs

The security community has long operated on a foundational belief: Sharing knowledge makes everyone safer. Researchers publish technical blogs, release proof-of-concept (POC) code, and distribute scanning templates to help defenders understand vulnerabilities, prioritize patching, and build better detections. This belief is not wrong, but it is incomplete. The same public research that helps defenders understand a vulnerability also hands adversaries a roadmap to exploit it. Analysis of weaponization timelines that CrowdStrike Counter Adversary Operations observed between January 2026 and July 2026 reinforces that in 2026, adversaries are rapidly adopting public vulnerability research, often within hours. The Window Is Closing Public vulnerability research (security advisories, technical…

CVEs
42
Highest CVSS
10
In KEV
20
Sources
43
Connections
146 relationships
PHPの重大欠陥「PHP2Shell」 4600万台中2900万台がいまだに脆弱
�Ǝ㐫���C������Έ���S�A�Ƃ͂����Ȃ��BPHP�̏d��ȐƎ㐫�uPHP2Shell�v�������ẮA�ً}�C���̌��J����U���������A�t�@�C�A�E�H�[����Ǘ��T�[�o25��̐N�Q���m�F���ꂽ�B�������APHP�̐Ǝ㐫���C��������ɂ��ʂ̌��ׂւ̑Ή����K�v�ɂȂ��Ă���B��2900����ɐƎ㐫���c�钆�A��Ƃ͉����m�F���ׂ��Ȃ̂��B ���̋L���͉������ł��B����o�^�i�����j����ƑS�Ă������������܂��B �@Kaspersky Lab�i�ȉ��AKaspersky�j��2026�N11��3���i���n���ԁA�ȉ����j�APHP�̏d��ȐƎ�i�������Ⴍ�j���uPHP2Shell�v�iCVE-2026-109618�ACVE-2026-109619�j������U�����ԂƖh�������\�����B���̐Ǝ㐫�͔F�Ȃ��ʼn��u����C�ӂ̃R�[�h�����s����鋰�ꂪ����APHP�𗘗p����Web�T�C�g�̖�70���ɉe������\��������B �@PHP�J����[����2026�N10��21���APHP 8.2�8.5�ɉ����A�T�|�[�g�I���ς݂�7.4�A8.0�A8.1�����ɂ��ً}�C��������B���J��15���ȓ��ɍU�����n�܂�Ƃ̗\�����o�Ă������AAmazon Web Services�iAWS�j�͏C�����J��4���O���爫�p�̎��s���ϑ������ƕ��Ă����B�����̍��ł͐��{�֘A�T�C�g���\�h�I�ɒ�~����A�uWikipedia�v�̃v���W�F�N�g�Ǘ��E�o�O�ǐՃV�X�e�����ꎞ�I�ɃT�[�r�X���~�����B �@2026�N10��21���ً̋}�C�����J�����2�T�Ԃ��o�߂��A���ۂ̐N�Q���m�F���ꂽ���A�L�͈͂ɔ�Q���g�傷��悤�ȑ�K�͐N�Q�͊m�F����Ă��Ȃ��Ƃ����B�������A�C���v���O�����̓K�p�͐i��ł��Ȃ��BCensys�ɂ��ƁA�����\�ȐƎ��PHP�o�[�W���������s����T�[�o��4600����̂����A��2900����ɐƎ㐫���c���Ă���B �@�C�����J������p�̎��s���������AAI�����p���č쐬���ꂽ�Ƃ݂���V���ȃG�N�X�v���C�g���o�ꂵ���BPalo Alto Networks�P���̕���͉��B�̐��{�@�ւɑ���U����������̂́A��ɂ��̔��\��P�Ă���B �@�����2026�N10��23���ɂ́APHP�ɕʂ̉��u�R�[�h���s�Ǝ㐫�uCVE-2026-115560�v�����������B����̐ݒ�ƃA�v���P�[�V�����R�[�h���g�ݍ��킳�������ň��p������������̂ŁAPHP�J����[���ً͋}�C���ł͂Ȃ��ʏ�̃A�b�v�f�[�g�X�P�W���[���őΉ�������j���������B�b���Ƃ��āusession.upload_progress.enabled�v�̖��������ē����Ă���B �@PHP2Shell�̎��ۂ̈��p�����t����ꂽ�̂�2026�N10��24�����BPerplexity�̃A�f���E�J���~�����^�p����PHP 8.4.26�̃n�j�[�|�b�g�ŁA2��IP�A�h���X����U�������������B�m�F���ꂽ�U���菇��CVE-2026-109618�Ɛ������Ă����B�������A���̃n�j�[�|�b�g�͍U�����������₷���uApache HTTP Server�v�́umod_php�v���������BCISA�i�č����y���S�ۏ�ȃT�C�o�[�Z�L�����e�B�C���t���X�g���N����Z�L�����e�B���j��2026�N10��26���A���Ǝ㐫���uKEV Catalog�v�iKnown Exploited Vulnerabilities Catalog�F���p���m�F���ꂽ�Ǝ㐫�J�^���O�j�ɓo�^�����B �@�����ADream Security�i�ȉ��ADream�j�͕č�����{�A��p�A�؍��Ńt�@�C�A�E�H�[���ƊǗ��T�[�o�v25�䂪�N�Q���ꂽ�ƕ����B���̂���3��͕Đ��{�֘A�Ƃ݂�����ɂ������B�U���҂�PHP2Shell�ɉ����ALinux�J�[�l���̐Ǝ㐫�uFragnesia�v�iCVE-2026-46300�j��g�ݍ��킹�Ĉ��p���A�V�X�e���̊Ǘ��Ҍ������擾�����Ƃ����B �@�N�Q�ɂ����LDAP�T�[�r�X�A�J�E���g�̃p�X���[�h�A���[�U�[��O���[�v�̈ꗗ�A�l�b�g���[�N�ݒ�A�閧���Ȃǂ��ގ悳�ꂽ�BDream��2026�N10��29���̍X�V�ŁA�Ώۂ�����o�[�W������PAN-OS�𓋍ڂ���Palo Alto Networks���@�킾�����Ɩ��炩�ɂ����B���������C���^�[�l�b�g�Ɍ��J���ꂽ�Ǘ��C���^�t�F�[�X�ւ̍U����F�߁A�Ǘ���ʂ̊O�����J��~�A�M���ł������IP�A�h���X�ւ̃A�N�Z�X�����A�C���v���O�����̓K�p���Ăъ|���Ă���B �@���ꂾ���[���ȐƎ㐫�ł���Ȃ���A�����_�ő�K�͐N�Q���m�F����Ă��Ȃ��w�i�ɂ́A�U�����������̕��G��������B �@Kaspersky�ɂ��ƁA�����Ŕ������ꂽ��1��9000��̋@��̂����A�U���҂��U���ΏۂƂ��đI�肵���̂�240�䂾�����BPHP2Shell�̈��p�́APHP�̃r���h������ݒ�A���N�G�X�g�̏��������A�A�v���P�[�V�����ŗL�̍\���Ȃǂɍ��E�����B���̂��߁A��������ŋ@�\���閜�\�ȍU���R�[�h����邱�Ƃ͓���Ƃ����B�Ȃ��A240��͍U���ΏۂƂ��đI�肳�ꂽ���ł���A�S�Ă̐N�Q���m�F���ꂽ�킯�ł͂Ȃ��B �@�������U���̐�������������I������Ƃ����āA���X�N���Ⴂ�킯�ł͂Ȃ��B�Ǝ�Ȋ������ɂ߂čU�������@���m�������A����̑g�D��V�X�e���ɔ�Q���W������\��������B �@��{�ƂȂ��́APHP���ŐV�̏C���łɍX�V���邱�Ƃ��B�������APHP2Shell�̏C����ɂ��lj��̑Ή����K�v�ɂȂ����B �@PHP�J����[����2026�N10��26���APHP�����p����O�����C�u����Brotli�ɑ��݂���Ǝ㐫�uCVE-2026-111497�v�ւ̏C�����܂ލX�V�ł����J�����B���̐Ǝ㐫�����p����ƁAPHP���H���ꂽ�O���T�[�o�̈��k���������������ۂɃR�[�h���s���������ꂪ����B�����ɂ͎��ۂ̈��p�����߂Ċϑ����ꂽ�B �@�C���ł�8.2.35-1�A8.3.36-1�A8.4.27-1�A8.5.12-1�BPHP2Shell�ւ̑Ή������łȂ��ABrotli�̐Ǝ㐫���C�����ꂽ�o�[�W�����ւ̍X�V���K�v���B �@�܂��A�p�b��K�p�����łȂ��APHP�𗘗p����V�X�e���S�̂̐N�Q�������������Ȃ��BKaspersky�͐N�Q�̒���Ƃ��āA�umultipart/form-data�v���܂ޕs�R��POST���N�G�X�g�A�uPHP_SESSION_UPLOAD_PROGRESS�v�ƃt�@�C���A�b�v���[�h�����̕s���R�ȑg�ݍ��킹�A�ʏ�ƈقȂ郊�N�G�X�g�T�C�Y��p�x�APHP�̃������s����HTTP 500�G���[�Ȃǂ������Ă���B �@�Ǝ㐫���C�����Ă��A�U���҂����ɐN�����Ă���Δ�Q��h����Ƃ͌���Ȃ��BPHP�𗘗p����R���|�[�l���g�̍X�V���m�F����ƂƂ��ɁA�N�Q�̍��Ղ��c���Ă��Ȃ����ǂ����ׂ�K�v������B Copyright © ITmedia, Inc. All Rights Reserved.
atmarkit.itmedia.co.jpNov 5, 2026extracted
Vulnerabilidades e incidentes de seguridad durante el octubre negro de 2026
Vulnerabilidades e incidentes de seguridad durante el octubre negro de 2026 03/11/2026 Mar, 03/11/2026 - 16:55 El 21 de octubre de 2026, PHP publicó correcciones para PHP2Shell (CVE-2026-109618 y CVE-2026-109619), GitLab para un fallo crítico de ejecución de código sin autenticación (CVE-2026-110264) y Node.js para una vulnerabilidad de Brotli (CVE-2026-111497). Estos avisos coincidieron con otros incidentes divulgados durante el denominado octubre negro de la ciberseguridad. Mozilla bloqueó ocho certificados intermedios de eMudhra por compromiso de sus claves. GoDaddy revocó certificados afectados por discrepancias en su documentación de emisión. LiteLLM retiró la versión 1.107.0, que contenía código malicioso. Railway y PingCAP confirmaron accesos no autorizados a sistemas con información de clientes. En PingCAP, los accesos habían comenzado en septiembre. Los parches de PHP, GitLab y Node.js están disponibles, y LiteLLM retiró los componentes comprometidos. Microsoft confirmó explotación activa de PHP2Shell y Brotli, mientras PingCAP seguía evaluando el impacto por cliente. La IA se utilizó en la investigación de PHP2Shell. Referencias 16/10/2026 GoDaddy (Mozilla Bugzilla) GoDaddy: Delayed Certificate Revocation 19/10/2026 PingCAP Security Update – October 2026 Security Incident Report: Unauthorized Access to PingCAP Cloud Resources 20/10/2026 Mozilla Protecting Firefox users following the compromise of eMudhra intermediate certificates 21/10/2026 PHP Security advisory: Critical remote code execution vulnerabilities, update now 21/10/2026 GitLab GitLab Critical Patch Release: 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10, 18.11.13 21/10/2026 Node.js Wednesday, October 21, 2026 Security Releases 21/10/2026 Wiz PHP2Shell: AI uncovers critical RCE vulnerabilities affecting 70% of the Internet 22/10/2026 Railway Preliminary Report: Oct 21st Security Incident 23/10/2026 LiteLLM The attack chain behind the v1.107.0 LiteLLM release 30/10/2026 Microsoft Security Response Center (MSRC) Patch now: PHP2Shell, Brotli, and eMudhra guidance for customers
incibe.esNov 3, 2026extracted
PHP2Shell: what we know about the threat two weeks later | Kaspersky official blog
Late October brought several unsettling cybersecurity stories all at once. Among these were two critical vulnerabilities in PHP, which potentially affected about 70% of websites worldwide. CVE-2026-109618 and CVE-2026-109619 — dubbed PHP2Shell — could let attackers execute code on a server remotely, without authentication. On October 21, PHP’s developers released emergency patches for the supported PHP 8.2–8.5 branches and for the unsupported PHP 7.4, 8.0, and 8.1. Experts predicted that attacks on vulnerable servers would start within 15 minutes of the updates going public. Amazon even reported exploitation attempts four days before the patches came out. With all this in the news, some organizations sounded the alarm early. For example, in several countries, government service websites were taken offline as a precaution. Even Wikipedia’s project management and bug-tracking system suspended service. Nearly two weeks have passed since the updates came out, but according to Censys data , of the 46 million scannable servers running a vulnerable PHP version, 29 million still contain the flaws. Right after the patches were published, we broke down each flaw in detail and explained what companies and everyday users should do. In this post we cover what’s known about the threat today, and what extra steps businesses need to take. What happened after the PHP2Shell patches The news about critical PHP vulnerabilities set off a flurry of reactions. Researchers noted a large number of exploitation attempts, and fresh exploits kept appearing in batches — courtesy of AI. A Palo Alto Networks unit even reported a PHP2Shell attack on a government agency in Europe, though it later retracted that statement. Solid evidence of how these vulnerabilities can actually be exploited only emerged later. On top of that, a third, unpatched one turned up. A vulnerability with no patch On Friday, October 23, the PHP team warned about a new vulnerability — CVE-2026-115560 — which can be used for remote code execution. But attackers can only pull this off on systems with an “unusual combination of configuration and application code”. That configuration is so exotic that the developers decided against an emergency patch, and will close the vulnerability on the regular schedule. In the meantime, they advised users to disable the session.upload_progress.enabled INI option. First signs of PHP flaws being exploited Let’s get back to the more serious threats. The most substantial confirmation of PHP2Shell exploitation in real-world attacks only came on October 24. Honeypot servers run by Adel Karimi of Perplexity running PHP 8.4.26 and presenting ordinary web pages recorded successful attacks from two IP addresses. The observed exploit chain was consistent with CVE-2026-109618. There’s an important caveat, though: the researcher’s honeypot ran the Apache mod_php module, which is the configuration most convenient for attackers. Later, on October 26, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added both CVE-2026-109618 and CVE-2026-109619 to its Known Exploited Vulnerabilities (KEV) catalog. That confirmed the threat isn’t just theoretical. Real-world breaches with PHP2Shell On October 26, the technology company Dream reported that 25 firewalls and management servers had been compromised in the U.S., Japan, Taiwan, and South Korea. Three of them were in an environment presumed to be linked to U.S. government agencies. The attackers combined PHP2Shell with a Linux kernel vulnerability dubbed Fragnesia ( CVE-2026-46300 ). Upon gaining full administrative control, they were able to extract the password of an LDAP service account and steal the listing of users and groups, full network configuration, and private keys. Dream initially didn’t name the device vendor. In its October 29 update, though, the company stated that the systems were Palo Alto Networks devices running certain versions of PAN-OS. The vendor confirmed attacks on management interfaces exposed to the internet. It urged customers to close public access to those interfaces, limit it to trusted internal IP addresses, and install patches. Why there are so few incidents Exploits are multiplying, but no wave of breaches has materialized, and the possibility of mass compromise of PHP servers remains unconfirmed. Even in the Palo Alto case, the scale of the attack was minimal: out of about 19 000 devices found, the attackers picked just 240, which were running software versions their exploit could handle. As it turns out, the existing PHP2Shell exploits aren’t one-size-fits-all. To exploit the vulnerabilities in a given environment, attackers have to account for the exact PHP build, memory settings, request handling, and application specifics. Still, the danger remains, so don’t neglect protective measures. How to stay safe The key advice stays the same: update. You can find the latest versions of the language on the PHP website . But installing patches isn’t enough. You also need to run a thorough audit of your systems and check every component that runs on PHP for signs of compromise. Why install the second round of PHP updates? Five days after releasing the emergency patches, the PHP developers published another round of fixes. The reason is that the updates that fixed PHP2Shell didn’t cover the CVE-2026-111497 vulnerability in Brotli, a third-party library. Exploiting this flaw can lead to code execution when PHP processes a specially crafted compressed response from an external server. The builds from October 25 include a patched version of the library. The latest PHP versions are 8.2.35-1, 8.3.36-1, 8.4.27-1, and 8.5.12-1. The first attack exploiting this vulnerability was recorded on October 26, so don’t put off installing the updates. Threat detection Possible signs of a PHP2Shell compromise include unusual POST requests that contain multipart/form-data media type, suspicious combinations of PHP_SESSION_UPLOAD_PROGRESS and upload parameters, atypical request sizes and request bursts, and HTTP 500 errors accompanied by PHP out-of-memory messages. Kaspersky solutions can help you spot the threat at different stages of an attack. Kaspersky NEXT EDR Expert promptly alerts you to suspicious activity running in the context of Linux and Windows web servers. Kaspersky Anti Targeted Attack (KATA) with the NDR module check network traffic for exploitation of the flaws described above. Kaspersky Vulnerability Management helps you find vulnerable versions of software. Kaspersky Managed Detection and Response detects exploitation of CVE-2026-109618 and CVE-2026-109619 by monitoring for behavior characteristic of RCE attacks. Kaspersky SIEM has been updated with new rules that help detect malicious activity typical of PHP2Shell. To learn more about how our solutions detect attempts to exploit PHP vulnerabilities, read our expert blog, Securelist .
kaspersky.comNov 3, 2026extracted
Product showcase: Sweet Virtual Patching stops HTTP2Shell while fixes catch up
Product showcase: Sweet Virtual Patching stops HTTP2Shell while fixes catch up HTTP2Shell (CVE-2026-111497), the critical Brotli bug first known as Node2Shell, is a remote code execution flaw in the compression library inside Node.js, Bun, Envoy, Python and more. AI found it: OpenAI’s agents turned it up in late September during a high-compute red-teaming campaign. Finding bugs is getting faster. Fixing them isn’t. HTTP2Shell shows why that gap matters, and how Sweet Virtual Patching protects running applications until the fixes land. A bad stream, a broken decoder Brotli’s decoder sits inside runtimes, HTTP libraries, proxies and frameworks, and it’s the first code to touch compressed data an attacker sends. As Sweet CTO Tomer Filiba explained, a malformed block-type switch can be read as a request for more input instead of an error, so the C decoder keeps going and writes past the end of an internal buffer. The result ranges from a crash to unauthenticated remote code execution, which researchers demonstrated against Node.js applications shortly after disclosure. AI finds it in one afternoon. You patch it for weeks Brotli isn’t one package. Sweet’s research team reproduced the same flaw in the most widely used Go port of Brotli, which sits underneath Traefik, Fiber and Iris. Each copy has to be fixed on its own: container images rebuilt and redeployed, single-executable apps recompiled, vendor bundles waited on. The window also opened long before disclosure. The root-cause fix landed in Brotli’s public source code on February 27, unrecognized as a security fix, and sat for close to eight months with no release or advisory. Diffing every commit to every popular library used to be impractical. For an agent, it isn’t. Attackers didn’t wait, either. In the weeks after disclosure, Sweet observed exploitation attempts in 88% of the environments it monitors. The industry’s answer so far has been more people: Bank of America CEO Brian Moynihan told CNBC the bank brought on 1,000 contractors to patch vulnerabilities surfaced by advanced AI models. Most organizations can’t do that, and none will out-hire the rate at which AI finds bugs. Patch what’s running first, cover the rest A CVE in an image tells you the vulnerable code exists, not whether it’s a risk. For that you need to know whether the library is loaded in a running process, whether that process decodes data an attacker can influence, whether the vulnerable code path has executed and whether the service is reachable from the internet. Those answers only exist at runtime, and they set the patching order. Anything that can’t be patched right away needs a compensating control. Disabling Brotli decompression works where the application doesn’t need it, as long as it’s disabled in the application and not only at a proxy. Where it can’t be turned off, virtual patching stops exploitation of that one flaw without a code change. It doesn’t replace the permanent fix, but it buys the time to do it properly. How Sweet Virtual Patching stops HTTP2Shell Sweet’s eBPF-based sensor watches processes, files, network traffic and application-layer requests in running workloads, without sidecars or code changes. Virtual Patching is built on that runtime view. See which services are actually exposed For HTTP2Shell in Node.js workloads, Sweet answers those runtime questions. In the example below, brotli-libs is loaded and executed in a card validation service that takes public inbound traffic and handles PCI data, so Sweet raises the CVE’s base score of 9.2 to a Sweet Score of 10. Sweet’s investigation view for CVE-2026-111497, with the vulnerable package mapped to a running, internet-facing service. Block the exploit in one click Once a team knows a service can be exploited, it can enforce a virtual patch in one click, with no code change or redeploy. For HTTP2Shell, the patch targets the point where the exploit does damage. When the Brotli decompression path tries to create a new process, the sensor blocks that system call. As Tomer put it, compression routines have no legitimate reason to spawn shells, so blocking the call stops the attack while legitimate traffic keeps flowing. When Sweet Attack, Sweet’s AI red-team agent, proactively proves a vulnerability is exploitable, it suggests the virtual patching policy for the team to enforce. The exploit path for CVE-2026-111497, with the clone system call blocked before the shell could start. See the patch working When Sweet blocks an attempt, it reconstructs the exploit step by step: 1. A crafted Brotli body sent to the service failed decompression and landed in the stream’s error path. 2. The vulnerable function ran. 3. The corrupted handle’s callback pointed at attacker-controlled code. 4. That code tried to launch a shell command to download and run a script. 5. The last step, the kernel call to create the shell process, was blocked. Security gets the evidence to treat the attempt as an incident, and engineering gets the exact frames behind the fix. Virtual Patching is available in supported environments. Sweet’s exploit chain for a blocked HTTP2Shell attempt, from malformed stream to the blocked process creation. Sweet covers the first 30 days Any organization concerned about HTTP2Shell can block it directly with Sweet Safety Net, an extension of Sweet’s Virtual Patching, and for no cost. Sweet covers 30 days of protection, starting at deployment. Final thoughts AI will keep finding bugs that have sat dormant for years in code that’s now almost everywhere. That’s good news, but it moves the bottleneck. Security teams used to be limited by what they knew about. Now they’re limited by how fast they can fix it. The teams that come out ahead will know which findings are running, reachable and being hit, and will virtually patch those while the permanent fixes catch up.
helpnetsecurity.comNov 3, 2026extracted
Milioni di server PHP nel mirino: scoperto come aggirare le difese e lanciare attacchi
I ricercatori di VulnCheck hanno imparato a sfruttare una critica vulnerabilità di PHP2Shell anche sui server con la protezione della memoria ASLR attivata. Il nuovo strumento permette di eseguire codice remoto senza autorizzazione e funziona con diverse versioni di PHP, ampliando significativamente le possibilità degli attaccanti. Il principale risultato è stato l’aggiramento della protezione ASLR sui server a 64 bit x86-64. Il meccanismo ASLR cambia casualmente la posizione del codice e dei dati del programma nella memoria operativa, rendendo difficile per i malintenzionati determinare in anticipo gli indirizzi necessari. In precedenza, tale protezione aveva notevolmente complicato la creazione di un exploit affidabile per PHP2Shell, soprattutto sui server di lavoro standard. Gli esperti di VulnCheck hanno risolto il problema con una catena di due azioni . Inizialmente, l’exploit estrae gli indirizzi dalla memoria del processo vulnerabile, rivelando informazioni che ASLR dovrebbe nascondere. Successivamente, le informazioni ottenute aiutano a ottenere l’esecuzione remota di codice arbitrario. La dimostrazione iniziale è stata condotta su PHP 8.4.26 con le impostazioni tipiche di un server di lavoro, inclusa la disattivazione dell’output degli errori tramite display_errors=off. Verso sera del 22 ottobre, i ricercatori hanno ampliato le capacità dello strumento. L’exploit aggiornato funzionava con PHP dall’8.4.10 all’8.4.26 incluso senza modifiche per ogni singola versione. Il risultato differisce significativamente dalle dimostrazioni progettate per una configurazione specifica della memoria. Tuttavia, la funzionalità confermata è ancora limitata al range di PHP indicato e alle condizioni di utilizzo verificate. Separatamente, VulnCheck ha testato i processori ARM64. I ricercatori sono riusciti a riprodurre la perdita di indirizzi di memoria, ma non sono riusciti a ottenere un’esecuzione remota completa del codice su tale architettura. Il team ha anche scoperto in pubblico un exploit dimostrativo che aggirava ASLR su x86-64, ma solo con PHP 8.4.26 e una configurazione standard della memoria dinamica. In altre condizioni testate, il prototipo pubblico non ha funzionato. Il proprio strumento più versatile, VulnCheck lo ha fornito a un gruppo limitato di clienti del servizio Initial Access Intelligence. Non è possibile scaricare liberamente lo sviluppo. I ricercatori avvertono che GitHub è già pieno di centinaia di repository con exploit di PHP2Shell apparentemente funzionanti, anche se solo una piccola parte del codice pubblicato utilizza effettivamente le vulnerabilità. L’emergere di uno strumento completo aumenta la probabilità di sviluppare nuove varianti di attacco funzionanti. La portata della potenziale minaccia è illustrata da uno studio separato dei server accessibili via Internet. VulnCheck ha scoperto 2.608.039 nodi con PHP. Di questi, 2.607.985, ovvero il 99,998%, sono stati considerati probabilmente vulnerabili a PHP2Shell. Il campione copre l’infrastruttura che il sistema di ricerca è stato in grado di rilevare e identificare, quindi non riflette il numero esatto di tutti i server PHP su Internet. Una situazione particolarmente preoccupante riguarda le versioni obsolete di PHP. Più di 1,1 milioni di server rilevati, circa il 42% del campione VulnCheck, utilizzano versioni per le quali il progetto principale non rilascia più release standard corrette. Più di 700.000 nodi funzionano con PHP da 3.x a 7.3, altri quasi 400.000 utilizzano le versioni non supportate 7.4, 8.0 e 8.1. Per le ultime tre, gli sviluppatori hanno preparato correzioni del codice sorgente, ma agli amministratori servono le build appropriate dai fornitori o l’installazione manuale delle patch. La parte più pericolosa di PHP2Shell è legata agli errori nell’interprete PHP stesso, non nel codice dei singoli siti. La vulnerabilità CVE-2026-109618 si verifica durante l’elaborazione errata della mancanza di memoria. Una richiesta appositamente formata può interrompere il funzionamento di PHP quando le strutture interne non sono ancora completamente preparate.  L'articolo Milioni di server PHP nel mirino: scoperto come aggirare le difese e lanciare attacchi proviene da Red Hot Cyber .
redhotcyber.comNov 1, 2026extracted
Suspected Chinese attackers built a custom PHP2Shell exploit and rooted 25 servers
Suspected Chinese attackers chained PHP2Shell with a Linux kernel privilege-escalation exploit to root 25 servers, including Palo Alto Networks firewalls linked to US government-affiliated organizations, according to Dream researchers. The snoops began exploiting these servers on October 23, targeting organizations across the US, Japan, Taiwan, and South Korea. The attackers also honed in on US government-affiliated firewalls. “Within hours of compromising a US government-affiliated firewall, they had tunneled into the internal network, compromised a third server using the same PHP2Shell exploit, and launched a full Active Directory attack campaign - all through a chain that started with a single unauthenticated HTTPS request to a management interface that should never have been exposed to the internet,” the Israeli AI cybersecurity startup said in a report. Plus, the attackers “likely still” have persistent, remote access to compromised organizations’ networks, Dream noted. The attackers rooted the first US government-affiliated firewall on October 23, but the device crashed shortly afterward, possibly due to around 900 MB of exploit traffic. According to Dream, it remained unresponsive despite 240 automated checks over two hours. They successfully exploited the second firewall a day later, on October 24. The compromised firewalls ran vulnerable versions of Palo Alto Networks' PAN-OS. Dream said it had been working with the vendor to investigate the compromises, and Palo Alto Networks' Unit 42 researchers independently verified the attacker's tooling and confirmed Dream's reported results. To break into the firewalls, the attackers built a custom exploit chain that includes PHP2Shell and a Fragnesia kernel flaw, and ran about 40 custom post-exploitation scripts once they were inside the targeted organizations. Total attack chain in under 15 minutes PHP2Shell, comprised of CVE-2026-109618 and CVE-2026-109619, came to light early last week, along with fears that attackers would abuse the bugs to take down most of the internet. Despite “hundreds” of PHP2Shell proof-of-concept repositories on GitHub, the first reports of successful attacks didn’t start until Saturday. Both bugs have CVSS scores of 9.2 and can be exploited without authentication to run code on vulnerable PHP servers. The PHP2Shell exploit recovered by Dream was not a copy of any known public exploit. It “appears to have been independently developed and tailored specifically for the targeted firewall platform,” the researchers wrote. The attackers combined PHP2Shell with Fragnesia (CVE-2026-46300), a high-severity local privilege-escalation vulnerability affecting the Linux kernel's XFRM ESP-in-TCP subsystem. The US Cybersecurity and Infrastructure Security Agency (CISA) added this Linux kernel bug to its catalog of Known Exploited Vulnerabilities on Wednesday. Both CISA and the FBI declined to comment. The miscreants developed a four-stage PHP2Shell exploit that allowed them to execute commands without authentication on vulnerable Palo Alto Networks firewalls. They then used Fragnesia to escalate their privileges and gain root access. The attackers targeted PAN-OS 12.1 and 12.2, which run PHP 8.0.30 with a high memory limit that enabled the exploit's memory-corruption stages. “The total chain - from unauthenticated HTTPS connection to persistent root webshell - completes in under 15 minutes,” the Dream team wrote. 4 steps to root Here’s how it works: First, they flood the servers with crafted multipart POST requests to corrupt PHP’s memory, and force a predictable memory layout. Then a second request forges the stale session ID length from the memory corruption part of the attack, forcing an out-of-bounds read and exposing the base address of libphp.so in the running process. The attackers then exhaust PHP's memory again to force mod_data=NULL, creating a stale reference they can forge in the final stage to execute commands as the nobody user. They use Fragnesia to escalate to root and plant a web shell in a publicly accessible directory on the firewall. After breaking in via the compromised firewalls, the attackers snooped around in Active Directory, stealing credentials and other sensitive information. With root access, the attackers also had the master key to decrypt the LDAP service account password, which they hardcoded into every subsequent script. They also enumerated every user and group in the domain via LDAP queries, and sprayed passwords against every user account. Attackers also tried to create backdoor AD accounts and attempted SAML signing key extraction - but Dream doesn’t know if these were successful. “The attack results - whether the password spray found valid credentials, whether the backdoor accounts were created, whether SAML keys were extracted - stayed on the management server's local filesystem and were not among the artifacts we recovered,” the researchers noted. AI tools in the attack The investigation also uncovered evidence that the attackers used AI tools, but noted that this was not a fully autonomous attack. The researchers found Anthropic's Claude Code installed, an AI-powered offensive security platform called aiscan configured with Chinese models DeepSeek and Kimi, and API keys for the FOFA reconnaissance service. FOFA is a Chinese internet asset search engine similar to Shodan. The attackers used it to identify about 19,000 internet-facing Palo Alto Networks firewalls worldwide. “The persistent tunnel into the US government organization is likely still running,” Dream warned. “And the attacker still has 19,000 fingerprinted targets they can revisit as they develop profiles for additional PAN-OS versions.”®
theregister.comOct 29, 2026extracted
Loading 3 more…
Related Stories
4
Chinese Hackers Quietly Used Low-Severity ESXi Logging Flaw as Zero-Day
The US cybersecurity agency CISA on Wednesday warned that hackers have been exploiting another VMware ESXi vulnerability in attacks. Tracked as CVE-2026-41709, the exploited flaw is described as a low-severity insufficient logging issue. It allows attackers logged in as administrators to perform certain operations without being logged. The security defect was disclosed on July 29 alongside three critical and one high-severity bug in VMware vCenter, ESXi, Workstation, and Fusion. VMware ESXi-9.1.0.0-25370933, ESXi-9.0.2.0100-25595025, and ESXi80U3j-25429389 and newer releases contain the relevant patches. CISA added CVE-2026-41709 to its Known Exploited Vulnerabilities (KEV) catalog, urging federal agencies to patch it within the next two weeks. CISA did not provide details on the observed exploitation, but CrowdStrike reported on Wednesday that the China-nexus threat actor Warp Panda had exploited CVE-2026-41709 as a zero-day in intrusions at US organizations, including law firms. According to CrowdStrike, Warp Panda typically gains initial access through internet-facing edge devices and pivots to VMware vCenter, where it deployed malware such as BrickStorm, TetanusStorm, SharpStorm, DualGauge and GuestConduit in intrusions throughout 2025. In several of those attacks, and as late as early 2026, the group used CVE-2026-41709 to significantly reduce audit trail visibility. At least two other security defects described in Broadcom’s July 29 advisories have been targeted in the wild, namely CVE-2026-59309 (a critical-severity authentication bypass) and CVE-2026-59310 (a critical directory traversal issue leading to arbitrary code execution). In mid-August, cybersecurity company Quirso said an APT had been exploiting CVE-2026-59310 to compromise approximately 360 web-accessible VMware vCenter servers and deploy an SSH reverse shell. Later, Quirso attributed the activity to a China-linked threat actor and warned that CVE-2026-59309 had been exploited as well, likely before CVE-2026-59310, potentially by a different threat actor. Mass targeting of CVE-2026-59310 was flagged in early September. Related: Chrome and Firefox Updates Patch Over 200 Vulnerabilities Related: TLS Flaws Found in GoAhead Web Server Used in Hundreds of Millions of Devices Related: China-Linked Hackers Exploit PHP2Shell to Root Firewalls Related: Long-Hidden Flaws Patched in EPICS Research Facility Control Software
77 shared
Nov 4, 2026
Worm armed 42 GitHub repos by hiding a payload too big to fail
Some attacks take real skill. Others just need someone to leave a door open. This week has both. Exposed passwords, old bugs still getting exploited, and trusted software doing things it shouldn't. There's a strange mix of clever tricks and careless mistakes. Hackers are borrowing trust from familiar apps, websites, and AI tools. Some are using AI to speed things up. Others are leaving their own attack files exposed. Not exactly careful work. Different stories, familiar weak spots. Here's what showed up this week. The threats change every week. Subscribe, and we’ll alert you when each new ThreatsDay Bulletin is out. PHP2Shell attacks persist WordPress security company Wordefence said it's not aware of any WordPress site compromised through PHP2Shell (CVE-2026-109618 and CVE-2026-109619) as of October 28, 2026. "We continue to see PHP2Shell-related requests across the more than 5 million sites we protect," it said. "Those requests show ongoing scanning and exploitation attempts; they do not show whether an attempt succeeded. Our site-cleaning and incident response teams have not handled a WordPress compromise attributed to these vulnerabilities." 40,573 secrets exposed Hudson Rock's investigation into the FortiBleed credential harvesting campaign has uncovered 975 newly identified domains and 40,573 exposed secrets, including 37,076 local-user records and 1,576 Active Directory LDAP bind records. The data comes from newly obtained 1,703 FortiGate source files associated with 1,689 host identifiers. "The configuration material dates to around February 2026, earlier than the likely May/June material examined in the first investigation," Hudson Rock said. The latest discovery has been codenamed FortiBleed 2.0. Institutional DNS hijacked Threat actors have used domain shadowing to place illegal gambling content beneath legitimate school and government domains in two unrelated operations. "In both cases, an unauthorized party appears to have gained access to DNS administration and created records that the original domain owners may not have noticed," Infoblox said. "Because the resulting hostnames sat within established institutional namespaces, they provided especially useful infrastructure for search-engine optimization (SEO) and traffic acquisition." One cluster, linked to a threat actor called Hidden Hawk, has been found to add individual CNAME records that mapped institutional hostnames to gambling pages hosted largely on Cloudflare Pages. The second campaign exploiting an Indian government domain "delegated entire subzones to third-party authoritative nameservers and used a wildcard, allowing many hostnames to be managed outside the victim's DNS environment." Put differently, the unauthorized DNS access creates new institutional hostnames, which resolve to infrastructure serving illegal gambling doorway pages. The pages also leverage the established reputation of school and government namespaces to ensure that the malicious URLs show up prominently in search engine results. AI banking credential warning Bank of America is reminding customers not to share banking credentials with AI agents. In an email blast to customers titled "Protecting your finances in the AI World," the financial institution urged customers to never share their username and password with another person or an outside service, "including an AI-enabled tool or agent that offers to act on your behalf." Android tightens contact access Google has announced that an upcoming Android release will no longer be able to directly write to contacts with the WRITE_CONTACTS permission. "Instead, you can use the standard contact intents (ACTION_INSERT, ACTION_EDIT, and ACTION_INSERT_OR_EDIT)," Google said. "Currently, if your app needs to save even one contact, you might be requesting WRITE_CONTACTS. But that permission grants broad access, allowing an app to make widespread changes to contacts across the device in the background, even without user interaction. Most apps don’t need such broad permission." 26,400 live credentials exposed A scan of 7.25 million public repositories on Gitee, China's largest indigenous Git hosting platform, has uncovered 26,400 unique verified-live credentials, including an active organization-admin credential for a major enterprise AI platform and thousands of live cloud provider access keys, independent security researcher Ben Zimmermann said. Critical Fortinet fixes released Fortinet has released a "coordinated set of security updates for FortiOS, FortiManager, and FortiAnalyzer" to address critical and high-severity flaws that were flagged using an AI-assisted vulnerability discovery approach. Details of the issues are being kept under wraps until November 10, 2026. With Fortinet devices becoming a favorite target for attackers, it's essential that users move quickly to apply the fixes. Zero-permission token theft Details have emerged about a now-patched flaw in Microsoft Authenticator (CVE-2026-80097 aka AuthMask) that could be exploited by installing and running a malicious application on an affected Android device and convincing the user to complete an authentication flow in the app by claiming to be a trusted app and getting the corresponding tokens. The flaw could be exploited to take over work accounts without requiring additional permissions. "Successful exploitation could allow the attacker to obtain authentication tokens and access resources as the affected user," Microsoft said. According to Enclave, "an unprivileged Android app with zero permissions could impersonate any installed Microsoft first-party app and have the Microsoft Authenticator broker hand it that app's tokens. The setup is a device with Authenticator installed and one work account signed into it." 32 fake AI bots hunt secrets Attackers are disguising themselves as AI agents to steal credentials. Cequence said it has tracked a single actor running AI agent impersonation at scale by posing as about 32 different AI bots, including ChatGPT, Claude, and Perplexity, while searching for passwords, API keys, and cloud credentials. "The malicious scanner runs from a major cloud provider and rotates through about 32 AI bot identities, spanning crawlers and assistants from OpenAI, Anthropic, Meta, Perplexity, and others," Will Glazier said. "It ignores web pages and requests files that commonly store secrets, including .env configuration files, cloud credential files, private SSH keys, and server environment data, working from a list of roughly 90 file paths. Each address sends a short burst of 50 to 190 requests in about eight seconds and then moves on. The scanner works through targets one at a time, around the clock, and first sends random nonsense paths to find websites that answer every request, a common scanning technique. It hit organizations in financial services, retail, telecommunications, energy, and software, and stayed active from at least late September through late October." China-linked network intrusion The U.S. Embassy in Fiji has revealed that hackers linked to China broke into a regional organization based in Suva between July and August 2026. "Hackers with links to China maintained access to the organization's network over several days," it said. The embassy did not name the threat actor. Nor did it disclose what data the attackers may have accessed. Camera software weaponized Attackers have been breaking into enterprise networks via camera management software, according to new research from security firm Huntress, which observed multiple incidents in September and October 2026 and traced them back to a compromised application. Source code artifacts point to a Korean company selling analog and IP cameras and digital and network video recorders. The activity abuses the legitimate "WpcMon.exe" binary to sideload DLLs that establish outbound connections to a remote server. "This activity demonstrates how attackers can blend malicious code with trusted Windows components to evade detection," Huntress said. 68 GB government data breach In a major operational security blunder, an unknown threat actor stole 68 GB from a Philippine government agency, maintained a detailed log of the transfer, then left that log open on the internet at 13.163.205[.]35:80. "The copy finished in under 24 minutes on September 6, 2026," Hunt.io said. "The transfer log records 27 SQL Server backups whose filenames correspond to the case-management systems of a Philippine overseas-employment and migrant-worker administration. Beside the log sat the operator's toolkit, a rebranded GodPotato build, a PowerShell stager, two payloads and a full Impacket environment." AI model data exfiltration concerns Canadian AI company Cohere has claimed that it caught Alibaba's Qwen3.8-Flash-Next model unsuccessfully attempting to send data to China from its evaluation sandbox as part of a prompt instructing the LLM to detect malicious file download and execution by monitoring for curl processes downloading bash scripts to /tmp followed by bash execution. "Asked to write a defensive detection rule, Qwen3.8-Flash-Next ignored instructions and inventoried the machine it was running on and then tried to upload a probe file to an Alibaba Cloud storage bucket in Beijing," Cohere said. "We cannot answer whether this is deliberate or a leftover glitch from training." Cohere has also released a dataset containing the model trace and corresponding raw token IDs in connection with the behavior. "The exact output is not guaranteed all the time, and many trials may be required to reproduce the behavior," Cohere said, adding "there are similarly unexpected URLs that the model also tends to output, most containing aliyunc." However, the findings have also led to social media chatter that the company is resorting to geopolitical fearmongering and that they are an attempt to clamp down on open-weights models. Post-quantum migration roadmap The U.S. National Institute of Standards and Technology (NIST) has released guidelines that detail the timelines for transitioning away from quantum-vulnerable algorithms to quantum-resistant standards. "The report describes different use cases and says why one migration might take longer than another," said NIST mathematician Dustin Moody, who heads the PQC standardization project. "We understand there's not one strategy that fits all use cases, and we want to help people handle their migration while staying abreast of what's changing." AI-powered ransomware operation exposed SOCRadar has uncovered the live workspace (i.e., open directory) of a threat actor tied to the n0n ransomware group, which exposed the operation's full workflow as of September 2026. The directory at 185.157.161[.]148 includes an AI coding agent configured with about 150 models to produce hundreds of attack scripts, with more than $7,216 in usage costs. "Entry points included a credential stuffing campaign against 305 FortiGate SSL-VPN devices, exposed AWS keys, weak RDP/WinRM credentials, and compromised hosting management portals," SOCRadar said. At least 23 organizations across 14 countries are said to have been identified in the workspace, including a U.S. sports retailer, a cloud provider, a teachers’ union, a Venezuelan ISP, an Argentine ministry and a pharmaceutical subsidiary. Government AI access restricted The Swedish government has barred employees from accessing browser-based versions of ChatGPT or Claude on their work computers over security concerns relating to the processing of sensitive data. "Officials were concerned that entering sensitive information into these models without an agreement setting out how to protect and secure the data could lead to it being fed into the model and stored for training," Euro News reported. 42 repositories hijacked JFrog and SafeDep have uncovered a campaign in which threat actors hijacked third-party 42 GitHub repositories across 11 owners to deploy payload blobs large enough "to evade the GitHub search and API paths normally used to find this kind of compromise." JFrog said, "The repositories contain execution hooks for AI coding assistants and IDEs, plus 12.9 to 13.7 MB polymorphic wrappers that all decode to the same hidden CI-publisher payload." The activity is assessed to be related to a Miasma-family npm worm propagated under various packages ending with "testmetest." According to SafeDep, the worm "shares code with Miasma 'Phantom Gyp' from June 2026 and adds the token-revocation wiper from Mini Shai-Hulud. The malicious versions steal credentials, spread to other packages and repositories, and install a wiper that deletes the home directory when the victim revokes the stolen GitHub token." Unsuspecting developers who installed the packages had their data stolen and repositories compromised with malicious code to produce further malicious testmetest releases and run shellpanel workflows targeting cPanel systems through CVE-2026-41940, overlapping with a prior campaign detailed by Socket in July 2026. Android banking malware-as-a-service A new Android malware operation called MR ROBOT is targeting customers of Indian banks and transforming banking fraud into a subscription business, with cybercriminals renting customized banking trojans to steal OTPs, card details, UPI PINs and credentials while secretly forwarding calls to bypass security checks. "It is not a single-actor campaign but a rented crimeware platform: a master operator leases access to affiliates, who use a Telegram bot ('APK Shield) and a web control panel (v7.0) to build personalized banking trojans on demand and distribute them through fake Play-Store-style pages and messaging-app lures," CloudSEK said. The kit impersonates around 36 lure apps, including banks, utility providers, and government services. One affiliate is estimated to have intercepted 5407 text messages from 153 infected devices. MDM platforms abused for remote access Threat actors are abusing legitimate mobile device management (MDM) platforms, like Hexnode and Rippling, by using social engineering to enroll devices or install management agents, per Huntress. "Once established, MDM provides a trusted, privileged path for malicious activity, such as deploying rogue RMM tools and maintaining remote access," it said. Critical Gotenberg RCE exploited Threat actors are exploiting CVE-2026-42589 (CVSS score: 9.8), a critical remote code execution flaw in Gotenberg, to deliver a Go-based reverse shell called "cache_base." The flaw was patched in May 2026. According to VulnCheck, the activity originated from a residential Japanese IP address in early October 2026. "The execution flow is straightforward: acquire a lock, collect host information, connect to C2, register the victim, and open a shell," VulnCheck said. Over the past 30 days, the vulnerability has recorded 1,358 exploitation events from 128 unique source IP addresses. Discord discussions go public Discord has announced it will allow search engines to index discussions in Discoverable Servers and make them accessible on the web to users outside the platform without an account or invitation, starting mid-December 2026. "Discussions in Discoverable Servers will soon be easier to find when you search the web, so you can find the answer you're looking for and step straight into the conversation on Discord," it said. The changes apply only to Discoverable Servers and do not extend to private servers and direct messages. 800+ ransomware victims claimed The Gentlemen ransomware operation has claimed more than 800 victims across multiple regions and sectors, with most attacks targeting organizations in the U.S. and Europe. "The group supports multiple platforms, with ransomware variants targeting Windows, Linux, NAS, and BSD systems, allowing its affiliates to target a broad range of enterprise environments," Acronis said. "The group's operations include the use of EDR-killing tools. In a recent incident, a custom dropper was observed deploying vulnerable Safetica ProcessMonitorDriver [CVE-2025-70795] and Lenovo BootRepair.sys drivers to terminate security processes." AI model loading RCE risk Pillar Security has disclosed an arbitrary-code-execution vulnerability in Unsloth's core model-loading path (CVE-2026-93348, CVSS score: 8.6). It has been fixed in unsloth_zoo 2026.8.14. "An attacker-controlled model configuration could cause Python code to execute during loading," researcher Ariel Fogel said. "The affected code ran inside the model-loading process, with access to whatever that process could read, modify, or authenticate to. In an AI development environment, that can include proprietary datasets, model artifacts, Hugging Face tokens, and cloud credentials. Exploitation required an affected loading path to process an attacker-controlled configuration." Unauthenticated root-level RCE XBOW said it identified an unauthenticated, critical-severity remote code execution bug in a public web application belonging to the U.S. Election Assistance Commission (EAC). "The vulnerable application was a resource/logistics calculator, not a voting machine or voter registration system," XBOW researcher Ariel Walter Garcia said. "The flaw allowed an unauthenticated attacker to execute code as root inside the backend container, with access to locally protected resources and outbound network connectivity, a privileged foothold reachable via a crafted unauthenticated web request." Session-hijacking RAT emerges A new remote access trojan called DarkCore comes with a dedicated browser that could let attackers access Gmail, WhatsApp, and MediaFire accounts using stolen sessions, while giving the impression that the activity is originating from the victim's own IP address. DarkCore was first advertised on cybercrime forums in August 2026. "The seller describes a browser that reuses those sessions to access work mailboxes, instant messaging apps, cloud storage and other services through the infected machine's IP address," BlackFog said. "The purpose is to make the access look like legitimate activity from the user." AI-powered malware framework Cisco Talos has disclosed details of a new AI-integrated command-and-control (C2) framework called NIK C2. The implant features surveillance, theft, lateral movement, and evasion capabilities, including credential dumping, RDP session hijacking, process hollowing, and a C2-driven screen lock ransomware module. "NIK C2 contains a Windows implant, using which, an actor can dump credentials, stream the victim's keystrokes to collect the targeted victim's sensitive data, and instruct an integrated AI model to analyze the harvested data, all within the compromised session," Talos said. "In this framework, the actor has abused the OpenAI Chat Completions application programming interface (API), which is an HTTP endpoint that enables ChatGPT-style conversations programmatically. In addition to the features that enable theft, an actor can also deploy desktop screen-locking ransomware via the NIK C2 implant onto the victim machine, leading to a ransom demand in Bitcoin or USDT cryptocurrencies." Three different versions of the malware have been identified to date since August 12, 2026. Talos said NIK C2 alters adversary tradecraft by collapsing collection and exploitation into a single continuous session. Malicious PDF delivers backdoor A phishing email using a FedEx tax invoice lure and containing a ZIP archive with a PDF has been observed triggering a multi-stage infection process to deliver a previously undocumented variant of the Sirius Backdoor. "The PDF abuses /OpenAction and /Launch objects to trigger an embedded Base64-encoded PowerShell command upon opening," Trellix said. "Execution relies on social engineering to trick the user into approving the PDF reader's security confirmation prompt. The PowerShell stager decrypts and reflectively loads a .NET assembly in memory. This loader performs process hollowing into legitimate Windows processes such as msbuild.exe, svchost.exe, etc., allowing the malware to operate under trusted process contexts." The final payload is SIRIUS, a Microsoft Visual C++ based backdoor with extended remote access capabilities. AI reshapes ransomware economics A new analysis from Flare has revealed that threat actors are building a mixed AI toolkit, combining commercial models with local, open-weight, and jailbroken alternatives, as well as leaning on stolen AI credentials to shift costs to victims. "Where AI can help is with understanding systems, writing tools and troubleshooting. The threat actor still needs access, decisions and a way to obtain payment," Flare said. "If AI helps an affiliate write a working data-export script without hiring a specialist, the affiliate may avoid that specialist’s fee and the wait for their help. AI makes expertise cheaper to obtain only when the cost of using and checking its work is lower than the cost of the specialist help it replaces." Emerging data-extortion threat A recently observed cyber-extortion actor named ScarlettGroup is publicly advertising alleged data compromises and uses negotiation deadlines and threatened disclosures to pressure targeted organizations. The group's dark web site listing includes victims from technology, education, government, and entertainment sectors. "ScarlettGroup demonstrates characteristics associated with financially motivated data-extortion operations, including public victim claims, deadline-based pressure, and underground forum activity," Foresiet said. "Its dedicated leak-site infrastructure and structured disclosure mechanism indicate an organized approach to promoting alleged compromises and exerting reputational pressure." Infostealers evolve into RATs Following its disruption in June 2026 as part of Operation Endgame, StealC has returned four months later as Stadia. "This time it's not a stealer: it's a full remote access trojan," Varonis said. "The RAT's features include hidden desktop control, a live command shell, a file explorer, a process manager and an in-memory loader, with StealC's stealer welded on as one module among six. The actor behind Stadia is working hard to win back original StealC customers: every former StealC customer is offered a free month on the top ($900) tier." The development comes as Moonlock Lab revealed that the Icarus macOS stealer has similarly evolved from a smash-and-grab crypto and data stealer to a malware with remote-access capabilities. The new iteration is called ICMacOS. "The stealer is actively advertised on cybercrime forums by a Russian-speaking actor operating under the handle GlowComa, with feature updates regularly announced via Telegram," SOCRadar said. "GlowComa promotes ICMacOS alongside Icarus ClickFix, a companion panel designed to deliver payloads using malicious copy-and-paste terminal commands. The infection chain relies on initial dropper scripts to detect the host architecture and harvest administrator passwords using fake system dialogs before delivering the primary payload." Another macOS-focused stealer is Aokigahara, which goes beyond browsers, VPN clients, cryptocurrency wallets, FTP/SFTP clients, password managers, and email applications to also target AI applications and development tools. "The stealer collects authentication files, session data, and configuration files associated with Claude, ChatGPT Desktop, Codex, Cursor, Windsurf, GitHub Copilot, Gemini CLI, and other tools," Check Point said. "Stolen AI credentials could offer opportunities for monetization. Usable credentials or session tokens could enable unauthorized access to paid AI services or the resale of compromised accounts." That's the week's mess. Some attacks were clever, some were painfully simple, and a few attackers made life easier for the people investigating them. The common problem? Too much trust in things nobody was watching closely. AI is adding new tricks, but the old ones aren't going anywhere. Stolen credentials, weak access controls, and forgotten bugs still get plenty of work done. New tools, familiar mistakes. The useful part is knowing where those mistakes keep showing up. That's usually where the next problem starts.
72 shared
Oct 30, 2026
Hackers Infect 953 Online Stores With Scanner-Evading Code
Attackers have infected 953 online stores, mostly running Magento, with a JavaScript loader that has evolved to tell security scanners apart from real shoppers. The campaign has been active since July 2025 and has cycled through five loader domains, according to research from Dutch e-commerce security firm Sansec. Its latest domain, registered October 6, was found in the content management system (CMS) blocks of 83 stores, 60 of which had carried an earlier version of the loader. The loader is stored in Magento's cms_block database table and has visitors' browsers fetch instructions from the attackers. Sansec said the server first works out whether a request comes from a genuine customer or a security scanner, and gives scanners nothing. Latest Loader Filters Security Scanners Before October, the operator relied on the Keitaro traffic distribution system to choose, for each visitor, between delivering a payload, redirecting the browser and returning nothing. The loader Sansec first found on October 7 instead called the new domain directly and replayed code saved in the browser, so anyone served the payload would rerun it on later page loads, even with the domain down or blocked. An October 23 rewrite added browser fingerprinting, checking for signs of browser automation and collecting hardware details, screen size, time zone and language before the server chose its response. When scanning service urlscan.io loaded an infected store in an automated browser, Sansec found no injected content. The company has yet to obtain the final payload, so the campaign's ultimate purpose remains unclear. Patches Did Not Always Stop Reinfection Sansec said a March wave planted the loader on 471 stores within an hour, using webshells placed through PolyShell (CVE-2026-48356). Among 169 infected Magento 2 installations lacking at least one core patch, 102 showed evidence of file uploads via PolyShell or SessionReaper (CVE-2025-54236). Patching alone did not prevent reinfection. A fully patched store running Magento 2.4.7-p10 picked up the newest loader on October 23, an hour after passing a clean scan. Sansec had spotted a rogue admin account and a GSocket backdoor on the store in September. Sansec advised merchants to look for the loader in CMS content, review admin accounts and hunt for backdoors, rotate database, admin and integration credentials once the store is clean and apply the latest Magento and Adobe Commerce security updates. It warned that removing the script leaves an attacker's write access to the database intact, so a compromised store can be reinfected while the original way in remains.
56 shared
Nov 2, 2026
Microsoft releases emergency .NET patches for critical Brotli flaw
A vulnerability in Google’s Brotli data compression library, tracked as CVE-2026-111497 and dubbed Node2Shell, has led to security updates from Microsoft, the Node.js project and the maintainers of two Python packages. Node.js and the Python packages were patched last week, and Microsoft followed on October 25 with fixes for .NET, Visual Studio and PowerShell. Bun, Envoy and Istio have also been updated. Brotli is a popular choice for compressing data sent over the web, and its decoder is embedded in a long list of applications and libraries. Described as an out-of-bounds write, the bug impacts Brotli 1.0.3 through 1.2.0. Google gave it a CVSS v4 score of 9.2, which puts it in the critical category. Brotli versions 1.0.10, 1.1.1 and 1.2.1 contain the fix. The Node.js project said specially crafted input can push data beyond the limits of a buffer used by the decoder. The resulting memory corruption could cause the process to crash or leak memory contents, and could also allow an unauthenticated attacker to run arbitrary code. Node.js credited the discovery to members of OpenAI Codex Security. According to OpenAI, the issue was uncovered during red-teaming work, after which the company notified the Brotli developers and the projects that rely on the library. OpenAI noted that the fix predates the disclosure. “This root cause issue was actually fixed in the Brotli source code in February, but it wasn’t known at the time that it gave rise to a security vulnerability and there was no more recent release of Brotli,” the AI company said. Code execution demonstrated on official Node.js image Imperva has shown that it can be exploited for code execution on the official Node.js 24.22.0 image for Linux arm64. Its researchers sent the malicious data both in a server response retrieved by the targeted application and in a request body processed by Express 5 or body-parser 2. “The proof did not succeed on every attempt. Our results establish code execution for the tested Linux arm64 build and application setups, and show how the fixed build handled the same inputs,” Imperva said. The security firm has not made its exploit public. Attacks only work if malicious Brotli data reaches the decoder, for instance through a library that unpacks compressed content on the application’s behalf. “Any application that passes attacker-controlled data to an affected Google Brotli decoder may be exposed. This includes compressed HTTP request bodies, responses fetched from untrusted servers, and compressed files,” OpenAI’s Patch the Planet initiative said in its advisory. No exploitation in the wild has been reported so far. A proof-of-concept exploit published on GitHub reportedly achieves code execution only against an intentionally weakened build, and some researchers argued the bug can only be used for denial-of-service (DoS) attacks. Microsoft products and Python packages affected Microsoft’s October 25 updates include .NET runtime versions 8.0.33, 9.0.22 and 10.0.14, along with .NET 11 Release Candidate 3. Visual Studio 2019, 2022 and 2026, as well as PowerShell 7.4, 7.5 and 7.6, have also been updated. Microsoft has categorized CVE-2026-111497 as an elevation of privilege issue with a CVSS v3.1 base score of 8.1. It rates the flaw critical for .NET and Visual Studio and important for PowerShell, and its exploitability assessment is “Exploitation More Likely.” In Python’s case, the vulnerable decoder is built into two PyPI packages, Brotli and brotlicffi. They have been patched with the release of versions 1.2.1 and 1.2.1.0, respectively. As more affected software emerged, researchers began referring to the flaw as HTTP2Shell and Broccoli2Shell. A public tracker of software that bundles its own copy of the Brotli decoder lists several projects that are still unpatched, including DuckDB, Apache Arrow, 7-Zip-zstd, p7zip and EDK II. Its maintainers say the list is incomplete, and that not every configuration of these projects necessarily exposes the vulnerable code. Applying the updates also requires restarting affected services and rebuilding container images on top of a patched base, since processes that are already running keep using the vulnerable code. Related: Mirai Botnet Operators Join PHP2Shell Attacks as ASLR Bypass Exploits Emerge Related: Attackers Exploit Third Arista VCO Zero-Day in Four Months Related: LiteLLM Compromised in Fresh Supply Chain Attack
38 shared
Oct 29, 2026