Twitxy Saved

ReliaQuest Threat Research

Verified account This account is verified. Learn more

@ReliaQuestTR

Tampa, Florida reliaquest.com/threat-researc… Joined May 2011
1.6K Following 7.9K Followers 8.2K Posts

Latest posts 5

ReliaQuest Threat Research Verified account @ReliaQuestTR
🚨 ReliaQuest observed threat actors abusing Claude chat-sharing notifications to deliver callback phishing.

Threat actors created Claude accounts with fake purchase alerts and callback numbers in the account name and chat title. Claude’s legitimate mail service then automatically sent and signed the sharing notifications. The observed emails passed SPF, DKIM, DMARC, and ARC and contained no malicious links or attachments for traditional security tools to evaluate.

The goal is to convince recipients to call a fake support number, where scammers may attempt to steal payment information or credentials or persuade victims to install remote-access software.

A legitimate sender and passing authentication checks do not make email content trustworthy. Employees should verify unexpected purchase alerts through the vendor’s official website and never call a number included in an unsolicited notification.

Organizations should review allowlists and spam-filter bypass rules for AI and SaaS notification domains, ensure these messages still receive content inspection, and monitor for similar abuse of sharing and invitation features across trusted platforms.
ReliaQuest Threat Research Verified account @ReliaQuestTR
🚨 ReliaQuest observed newly registered domains likely impersonating Canadian banks. Registered through NiceNic today (October 26), both combine bank branding with “secure” and “2FA” wording that could make fraudulent authentication requests appear credible.

• [organization]2fasecure[.]com
• [organization]secure2fa[.]com

If used for phishing, this infrastructure could lead to credential theft, MFA code interception, unauthorized account access, and financial fraud.

Security-themed wording does not make a domain trustworthy. Access online banking through official apps or known bookmarks, verify unexpected authentication requests directly with your bank through established channels, and avoid sharing verification codes with unsolicited callers. Organizations should monitor newly registered domains for bank impersonation and MFA/2FA-themed lures.
1 replies 1 reposts 12 likes 1.9K views View on X
ReliaQuest Threat Research Verified account @ReliaQuestTR
🚨 ReliaQuest has observed operators using ARTEX, a publicly available AI-driven penetration-testing console, to automate attacks against internet-facing e-commerce and payment applications. ARTEX can rapidly chain common application-security weaknesses, including exposed API keys and insecure file uploads, to deploy web shells, access databases, steal secrets, attempt lateral movement and perform payment-related actions within hours.

Potential indicators include the artex-enrich/1.0 user agent, shell names containing artx or artex followed by five digits, multipart boundaries beginning with ----artx, and executable files written to upload directories. These artifacts may change, so behavior-based detection remains critical.

Remove secrets from client-side code, harden upload features, protect test systems like production, and monitor web-server processes for shell execution, discovery commands and executable file creation.
ReliaQuest Threat Research Verified account @ReliaQuestTR
🚨 ReliaQuest researchers independently reproduced exploitation of CVE-2026-109618 in controlled lab environments, revealing a promising sequence of server-side detection signals.

Defenders should look for a POST request returning an HTTP 500 error, followed within seconds by:
• PHP memory exhaustion containing in Unknown on line 0
• zend_mm_heap corrupted
• An Apache worker crash with AH00052 and Abort (6)

These events may be benign individually, but the full sequence, particularly when correlated by process ID, provides a much stronger indication of exploitation. Organizations should collect PHP error, web-server access, web-server error and system logs, and configure access logs to include the worker PID.

Endpoint monitoring should also identify PHP or web-server processes launching shells, running discovery commands, downloading tools, making unexpected outbound connections or creating potential web shells.

Patch immediately and ensure PHP, web-server, system and endpoint telemetry is available for hunting. ReliaQuest has not observed successful exploitation in customer environments.

Read more: reliaquest.com/blog/threat-sp…
reliaquest.com PHP2Shell: Responding to Critical PHP Vulnerabilities | Threat Spotlight PHP2Shell (CVE-2026-109618 and CVE-2026-109619) lets unauthenticated attackers run code on PHP web servers. PHP released fixes on October 21, 2026.
1 replies 3 reposts 15 likes 1.3K views View on X
ReliaQuest Threat Research Verified account @ReliaQuestTR
🚨 PHP2Shell may begin with malicious requests that blend into routine scanning, but the activity that follows should be more recognizable.

ReliaQuest assesses that threat actors will use code execution to expand access by spawning shells, running discovery commands, downloading tools, establishing persistence, and moving laterally. This can turn a PHP exploit into broader server compromise, data theft, and operational disruption.

Patching closes the vulnerability but will not remove existing access. Organizations should patch immediately, rotate exposed secrets, and use behavioral detections and retrospective hunting to identify post-exploitation activity.

Read the full assessment:
ow.ly/ySiy50ZZOmA

#ReliaQuest #ThreatResearch #AgenticAI