World

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has confirmed that two recently patched PHP2Shell vulnerabilities are being actively exploited in the wild, adding them to its Known Exploited Vulnerabilities (KEV) catalog. Both flaws carry a CVSS score of 9.2 and allow unauthenticated remote code execution on affected deployments.

The vulnerabilities are tracked as:

• CVE-2026-109618 — an out-of-memory condition that can be triggered without authentication, according to the available details.

CISA's addition of these issues to the KEV catalog signals that exploitation has been observed rather than merely theoretical, so organizations running affected PHP deployments should treat patching as urgent. The agency has not published additional technical specifics beyond the remote code execution impact and the critical severity rating.

Administrators should review their PHP2Shell installations, apply the vendor patches released for both flaws, and check for signs of compromise on any systems that may have been exposed prior to patching. Given the unauthenticated nature of the attack vector, internet-facing deployments warrant the highest priority.

Source: The Hacker News

Has your organization already applied the patches for these PHP2Shell flaws, or are you still working through exposure assessment?

A memory-corruption vulnerability in Google's Brotli decoder has a much wider reach than initially thought, extending well beyond the Node.js remote code execution issue that first brought it to attention. The flaw, tracked as CVE-2026-111497, allows specially crafted compressed data to write past the end of a buffer, corrupting the affected program's memory.

Because the decoder is embedded in a broad range of software that unpacks Brotli-compressed data, the exposure is not limited to a single platform. Confirmed affected software includes:

• Bun
• Microsoft .NET
• The Python Brotli and brotlicffi packages
• Envoy proxies configured to decompress Brotli

Any application or service that accepts untrusted Brotli-compressed input and relies on an unpatched decoder should be treated as potentially at risk. Administrators are advised to identify where Brotli decompression is exposed to external input and apply vendor updates as they become available.

Source: The Hacker News

Does your organization rely on any of the affected Brotli implementations, and how are you handling the patch?

An unknown threat actor has compromised 953 online stores, the majority of which run Magento, in a campaign that has been active since July 2025. The activity was detailed by Dutch e-commerce security firm Sansec, which describes the operation as designed to inject a small piece of code into store pages so that malicious JavaScript loader code is served to unsuspecting visitors through Magento CMS blocks.

The loader is reportedly built to evade detection by scanners, making it harder for store operators and security tools to spot the compromise through routine checks. Sansec notes the campaign has persisted for months, suggesting the attackers are maintaining access across a large number of storefronts rather than conducting a short-lived burst of activity.

Key facts so far:

• 953 online stores infected
• Most affected stores run Magento
• Campaign active since July 2025
• Malicious JavaScript loader delivered via Magento CMS blocks
• Code is designed to evade scanner detection

Store owners running Magento should review their CMS blocks for unexpected or obfuscated code and audit recent administrative changes, particularly anything dating back to July 2025. Given the scanner-evading nature of the loader, manual inspection of page content and block configurations is advisable rather than relying solely on automated scanning.

Source: The Hacker News

Is your organization running Magento, and have you checked your CMS blocks for signs of this loader?

South Korean police have identified seven suspects tied to a cybercrime operation that compromised more than 90 organizations across the country. According to investigators, the group relied on the ARTEX AI pentesting framework to carry out most of the attacks, a detail that stands out given the tool's origins in legitimate security testing.

The operation reportedly led to the theft of 8.2 million data records, and the case has drawn attention because at least one of the accused is a former pentester — someone with hands-on experience in offensive security techniques. That background likely made it easier to adapt professional-grade tooling like ARTEX AI for criminal purposes rather than authorized assessments.

Key points from the report:

• Police in South Korea identified seven suspects in connection with the campaign
• More than 90 organizations were breached
• The ARTEX AI pentesting framework was used in the majority of the attacks
• A former pentester is among those accused
• Roughly 8.2 million records were stolen

The case underscores a familiar concern in the security community: tools built for authorized penetration testing can be repurposed with little friction when they fall into the wrong hands. It also highlights how AI-assisted frameworks are lowering the effort required to scale attacks across many targets.

Source: Unknown

Does your organization have controls in place to detect abuse of legitimate pentesting tooling, and how are you handling that risk?

The University of Copenhagen has disclosed a data breach after hackers gained access to one of its internal test environments. The exposed environment contained personal data belonging to approximately 525,000 people, making this one of the larger education-sector breaches reported in Denmark.

According to the university's confirmation, the compromised system was a test environment rather than a production system, though it still held real personal data. Details on exactly what categories of information were exposed, how the attackers got in, or when the intrusion was detected have not been fully detailed in the initial reporting.

Key facts as confirmed so far:

• Affected organization: University of Copenhagen (Denmark)
• Number of individuals exposed: 525,000
• System involved: a test environment containing personal data
• No specific CVE ID or advisory identifier has been cited in connection with this incident

The university has stated it is investigating the incident and will likely provide further guidance to affected individuals as the review progresses. Those who may be impacted should watch for official communications from the university and be cautious of phishing attempts referencing the breach.

Source: Unknown

Do you think test environments holding real personal data are an underrated exposure risk in your organization?

DreamHost is requiring password resets for email and FTP/SFTP users following an ongoing incident that disrupted connections to its File Manager interface, according to reports. The hosting provider has moved to force credential changes as part of its response to the disruption.

Details remain limited at this stage, and no specific indicator of compromise, advisory identifier, or root-cause information has been disclosed in the reporting. Customers who rely on DreamHost for email or file transfer access should treat their credentials as potentially affected and complete the reset process if they have not already done so.

• Affected services: email and FTP/SFTP accounts
• Reported symptom: disrupted connections to the File Manager interface
• Action taken: forced password resets for affected users

Source: Publication Name

Have you received a reset notice or noticed File Manager issues on your DreamHost account?

Microsoft has pushed out emergency security updates for .NET to address a critical vulnerability that has been given the name Broccoli2Shell, and is also tracked as Node2Shell and HTTP2Shell.

The flaw is rated critical and affects the Brotli decompression component within .NET. Microsoft is treating this seriously enough to release the patches outside of its normal update schedule, so administrators running affected .NET deployments should prioritize testing and deployment.

At this time, the details available are limited to what Microsoft has published in its emergency advisory. The company has not disclosed the full technical specifics of the vulnerability, and no specific CVE identifier has been provided in the source reporting. That means defenders should rely on Microsoft's official guidance and patch information rather than assuming a particular CVE number.

Given the critical rating and the emergency nature of the release, the practical takeaway is straightforward:

• Identify any systems, services, or applications that depend on .NET and the Brotli decompression path.
• Apply the emergency .NET updates as soon as possible.
• Monitor Microsoft's advisory channels for further technical details and any updates to the tracking information.

Because the disclosure is still developing, expect additional details to emerge in the coming days.

Source: Unknown

Are any of your environments running .NET services that could be exposed to this Brotli flaw, and how are you handling the emergency patching window?

How to I Hacked a Sri Lankan Ministry of Health Website

Step 1: Target Selection

Every security investigation starts with identifying a target. I began by examining a publicly accessible website associated with Sri Lanka’s Ministry of Health.

Step 2: Manual Endpoint Discovery

I manually explored the website and identified an endpoint that caught my attention:

g_hospital.php?id=61

The id parameter became the focus of my investigation.

Step 3: Initial Testing

I added a single quotation mark (') to the parameter and observed the response.

The website displayed a blank page. This was an interesting observation, although it was not sufficient on its own to confirm a vulnerability.

️ Step 4: SQLmap Analysis

I then used SQLmap, a tool for testing SQL injection vulnerabilities, to investigate the parameter further.

The command I used was:

sqlmap -u "TARGET_URL" --level 5 --risk=3 --random-agent --tamper=space2comment,randomcase --threads 10 --dbs

The options configured more extensive testing, modified request patterns, and requested database enumeration if a vulnerability could be exploited.

Step 5: The Reported Result

According to my account, the SQLmap test succeeded.

A successful result from SQLmap can indicate that an injectable parameter was identified and that database information was accessible. The exact impact depends on the tool's output and what it actually confirmed.

️ Final Thoughts

This investigation highlights the importance of manual endpoint discovery, understanding application responses, and using security testing tools to investigate potential vulnerabilities.

Responsible security research means documenting evidence, respecting authorization, and reporting vulnerabilities so they can be fixed.

#CyberSecurity #SQLInjection #SQLmap #EthicalHacking #WebSecurity #PenetrationTesting #SriLanka

A critical vulnerability dubbed HTTP2Shell has been identified in Brotli, the C decoder library bundled with Node.js. The flaw could allow attackers to corrupt memory and gain access to sensitive data, prompting emergency patches from maintainers.

Because the issue affects the decoding library that ships with Node.js, applications and services that process Brotli-compressed input may be exposed. Memory corruption issues of this kind can potentially be leveraged beyond a simple crash, making prompt patching important for anything relying on the affected library.

At this stage, the available details center on the memory corruption impact and the emergency patch response. Administrators running Node.js or other software that embeds Brotli should treat this as high priority and apply vendor updates as soon as they are available.

• Review your Node.js and Brotli dependencies for affected versions
• Apply the emergency patches released by maintainers promptly
• Monitor vendor advisories for further technical details and updated guidance

Given the severity, don't wait for a full exploit breakdown before patching.

Source: Unknown

Are your Node.js services already patched, or are you still assessing exposure?

Two critical vulnerabilities have been disclosed in Wasmtime, a WebAssembly runtime that can be embedded into other software. According to the project's maintainers, both flaws could allow a malicious WebAssembly module to break out of the sandbox that is meant to contain it.

Exploitation requires the attacker to get a vulnerable Wasmtime build to compile a module they control — the flaws are not remotely triggerable on their own. One of the two issues impacts only ARM64 systems, so exposure depends heavily on the underlying architecture in use.

Fixed versions of Wasmtime have been released, and operators running the runtime — directly or as a dependency inside another application — should upgrade to the patched release as soon as possible.

Mitigation guidance:

• Identify any software in your environment that bundles or embeds Wasmtime.
• Upgrade to the fixed release published by the maintainers.
• Pay particular attention to ARM64 deployments, which are affected by one of the two flaws.
• Avoid compiling or running untrusted WebAssembly modules on unpatched builds.

Source: The Hacker News

Does your organization embed Wasmtime in any production software, and have you already patched it?

Kali Linux 2026.3 has arrived as the distribution's third release this year, bringing a set of new offensive security tools alongside desktop environment refinements and updated build scripts.

The headline addition is a batch of new hacking tools packaged into the release. The update also includes improvements across the desktop experience and refreshed build tooling, keeping the platform current for penetration testers and security researchers.

Key points from the release:

• Six new tools added to the Kali toolset
• Desktop environment improvements
• Refreshed build scripts
• Third release of the year, continuing Kali's regular cadence

Users are encouraged to update existing installations or grab fresh images from the official Kali downloads page to take advantage of the new tooling.

Source: Unknown

Have you tried any of the new tools in this release yet, and how do they fit into your workflow?

A developer's AI coding agent was nearly tricked into installing a known-malicious npm package by a malicious instruction file placed in their Downloads folder, according to a report published last week by Forever Security.

The security firm detected the attempt on a real customer's machine and intervened before any code was executed. Investigators were unable to determine how the file ended up in the Downloads folder in the first place.

Key points from the report:

• The attack relied on a malicious instruction file dropped in a commonly used directory (Downloads) rather than a traditional exploit.
• The file attempted to direct the AI coding agent to install a known-malicious npm package.
• Forever Security stopped the agent before any code ran, so no execution occurred on the affected machine.
• The initial infection vector remains unknown, as the firm could not establish how the file was placed in the folder.

This incident highlights a growing risk surface around AI coding assistants, which often read files and act on instructions from the local environment. Developers running such agents should be cautious about unexpected files in download or working directories and review what their tools are permitted to install automatically.

Source: The Hacker News

Does your organization restrict what your AI coding agents are allowed to read or install from local directories?

PHP has pushed out emergency updates addressing two critical vulnerabilities in the PHP language itself that could allow an unauthenticated attacker to execute code on a web server. The fixes are available in PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35, and according to the PHP team, only applying the update provides full protection for a server.

The two flaws, collectively tracked as PHP2Shell, reside in the PHP runtime rather than in any application layer. This means a site can be exposed even when its own code is not at fault, since the weakness exists beneath whatever application is running on top of the interpreter.

Key points for defenders:

• The vulnerabilities are unauthenticated, requiring no account or credentials to exploit.
• Because the flaws sit in the runtime, patching the application code or hardening the site will not remediate them.
• The affected update branches are 8.5.x, 8.4.x, 8.3.x, and 8.2.x, with fixes landing in the point releases listed above.
• The PHP team's guidance is clear: updating is the only complete protection.

If your organization runs PHP in any capacity, treat this as urgent and verify which version your servers and containers are running before the weekend.

Source: [email protected] (The Hacker News)

Has your team already confirmed which PHP versions are running across your environments, or are you still mapping affected hosts?

The LiteLLM Python package has been compromised in a software supply chain attack that delivered a credential stealer and a backdoor, according to findings from SafeDep, Socket, StepSecurity, and Upwind.

The affected release is LiteLLM 1.107.0, which was distributed through PyPI wheels and Docker images. The package has since been quarantined on the Python Package Index (PyPI).

If your environment pulled this version, treat any credentials accessible to it as potentially exposed and review your dependency lockfiles and container images for the affected release.

Source: The Hacker News

Has your organization pinned or deployed LiteLLM 1.107.0, and if so, what steps are you taking to rotate credentials and verify your images?

GitLab has released fixes for a critical vulnerability that allows an attacker to execute code on a self-managed server without authentication. The flaw carries a CVSS score of 10.0 and affects every version of the software going back to 7.0, which was released in 2014 — meaning roughly twelve years of releases are impacted.

The October 21 patch is significant even for administrators who updated nine days earlier. The October 12 update only covered versions 19.2 and later, and the newly fixed versions sit one patch above it, so anyone who applied that earlier release remains exposed.

Key points for defenders:

• The vulnerability enables unauthenticated remote code execution on self-managed GitLab instances.
• All versions from 7.0 onward are affected.
• Fixes were published on October 21.
• The earlier October 12 update addressed only 19.2 and later and does not cover older branches.
• Administrators should move to the latest patched release rather than relying on the earlier update.

Given the breadth of affected releases and the lack of authentication required, self-managed GitLab operators should treat this as urgent and verify their current version against the latest fixed release.

Source: The Hacker News

Has your organization already applied the October 21 patch, or are you still running a release from before 19.2?

Microsoft has attributed the recent supply chain compromise of the ConnectWise Cloud Backup application to a China state-aligned threat actor tracked as Storm-0940.

According to Microsoft's disclosure on Wednesday, the group leveraged ARTEX, a Go-based agentic AI penetration testing framework, during the incident. ARTEX was subsequently made closed-source following its abuse in cyber attacks targeting South Korean financial institutions. The framework was used to accelerate the intrusion.

Key points:

• Threat actor: Storm-0940, a China state-aligned group
• Targeted application: ConnectWise Cloud Backup
• Tooling: ARTEX, a Go-based agentic AI penetration testing framework
• ARTEX was moved to closed-source development after being abused in attacks against South Korean financial institutions

Organizations using ConnectWise Cloud Backup should review their exposure and monitor for signs of compromise tied to this supply chain incident.

Source: The Hacker News

Is your organization running ConnectWise Cloud Backup, and if so, what steps are you taking to assess exposure?

Amazon's Threat Intelligence team has reported that an exploitation attempt targeting the newly disclosed PHP2Shell vulnerabilities was detected as early as October 17, 2026, against its MadPot honeypot service. This predates the public disclosure of the flaws and indicates possible prior knowledge or opportunism before patches became widely available.

The attempt originated from an IP address tied to a commercial anonymization network, suggesting the actor sought to obscure their origin. Following the release of patches, the PHP2Shell flaws have now come under broad exploitation in the wild, making timely patching and monitoring especially important for exposed systems.

At this time, the article does not provide specific affected version details, indicators of compromise, or mitigation guidance beyond applying the available patches and watching for exploitation activity. Administrators running PHP-based services should prioritize patching and review logs for suspicious requests.

Source: The Hacker News

Has your organization applied the PHP2Shell patches yet, and have you observed any exploitation attempts in your logs?

Threat actors are actively exploiting the PHP2Shell vulnerabilities, tracked as CVE-2026-109618 and CVE-2026-109619, with global scanning activity observed and signs that attackers are leveraging agentic artificial intelligence platforms during post-exploitation.

In one notable incident, attackers targeted a government entity in Europe. Within two hours of the initial exploitation, they had successfully accessed password hashes and multi-factor authentication data, according to reporting on the campaign. The use of AI-assisted tooling in the post-exploitation phase marks a concerning shift, as it appears to accelerate the speed at which attackers move from initial access to credential theft.

Key points from the reporting:

• Exploitation centers on the PHP2Shell vulnerabilities, CVE-2026-109618 and CVE-2026-109619
• A European government entity was compromised, with password hashes and MFA-related data accessed within two hours of exploitation
• Global scanning for vulnerable systems is underway
• Threat actors have been observed using agentic AI platforms for post-exploitation activity

Organizations running affected PHP-based systems should prioritize patching and review authentication logs for signs of compromise, particularly unusual access to credential stores or MFA configurations.

Source: [email protected] (The Hacker News)

Has your organization scanned for exposure to these PHP2Shell vulnerabilities yet, and if so, what did you find?

A researcher has disclosed that Tailscale SSH can be abused to escalate from a single compromised device to root on other reachable servers. The attack hinges on two preconditions: Tailscale SSH configured to permit port forwarding, and an attacker who already controls one device that the network's access rules allow to connect to the target.

The flaws remain unpatched at the time of reporting, so the exposure is a configuration and trust-boundary issue as much as a software one. Any environment relying on Tailscale SSH for administrative access should review whether port forwarding is enabled and how broadly its access rules permit device-to-device connections.

• Port forwarding through Tailscale SSH is a prerequisite for the attack
• The attacker must already control a device that access rules permit to reach the target
• No patch is currently available, per the report

Until a fix ships, tightening access rules and disabling unnecessary port forwarding limits the blast radius of a single compromised endpoint.

Source: The Hacker News

Does your organization rely on Tailscale SSH for server access, and have you reviewed your port forwarding settings in light of this?

Researchers have identified a new attack vector targeting AI coding agents, after finding a malicious AGENTS.md instruction file sitting in a customer's Downloads folder. The file was crafted to manipulate the AI agent into installing a rogue npm package, turning a routine developer workflow into a supply chain risk.

The technique abuses the way AI coding assistants automatically read instruction files such as AGENTS.md to understand project context. Because the agent trusted the file without questioning its origin, it followed the embedded instructions and pulled in the malicious dependency.

Key points for defenders:

• Treat AGENTS.md and similar agent instruction files as executable content, not harmless documentation
• Monitor Downloads folders and project directories for unexpected instruction files
• Restrict AI coding agents from automatically installing packages without review
• Audit npm dependencies for packages introduced by automated tooling

This highlights a broader concern: as AI coding agents gain autonomy over file reads and package installs, the trust boundary between "content" and "instructions" becomes a real attack surface.

Source: Unknown

Does your organization review instruction files like AGENTS.md before letting AI agents act on them?