FBI Warns of ARTEX AI Pentest Framework Abused by Cybercriminals with Backdoored Docker Images
The FBI has issued a public warning about the ARTEX open-source AI-driven penetration testing framework after confirming its use by cybercriminals in targeted operations against banks, governments, and technology companies.
Since August 2026, operators have leveraged the tool to obtain privileged access in less than three hours during several intrusions. The alert raises serious concerns about the integrity of the framework itself, particularly for security professionals considering deployment in corporate environments.
Backdoored Docker Images Identified
The Cloud Security Alliance documented malicious Docker images of ARTEX containing a backdoor capable of executing commands as root without authentication. The mechanism relied on a hidden value in the CAPTCHA field to trigger commands via sh -c, bypassing normal login procedures. The malicious code was absent from the original repository and present only in pre-built images.
One compromised image accumulated roughly 9,000 downloads, while 62 exposed consoles were identified running the adulterated version. This means even professionals who reviewed the source code could miss the compromise prior to installation.
Significant Data Exposure Risks
ARTEX can store AI API keys, credentials, authenticated sessions, discovered vulnerabilities, and detailed corporate network information. A compromised instance could expose the most sensitive data from security operations and, depending on container configuration, enable further compromise of connected systems.
The Check Point research team identified 1,608 internet-accessible ARTEX consoles, including ten instances with exposed databases. A tool intended to find vulnerabilities can therefore become an entry point for attackers.
Autonomous Agent Concerns and Repository Removal
According to CERT-EU, the framework lacks strict technical controls to prevent actions outside authorized scope, relying instead on configurable rules and AI model behavior. This creates notable risk when agents can execute commands, manipulate files, and interact directly with internal systems.
The original repository was removed from GitHub in October, yet forks and third-party images continued to circulate, amplifying concerns over provenance, integrity, and security of available distributions.
Related articles
Uber Breach Exposes 149,000 Drivers After Third-Party Vendor Credentials Stolen
Uber has notified approximately 149,346 drivers that personal data was stolen in an October incident involving a compromised third-party vendor. Attackers used valid credentials belonging to the vendor to access data the ride-hailing company had shared with it, bypassing all security alerts because the access appeared legitimate. The affected information includes driver license images, names, addresses, dates of birth and government-issued identification numbers. The vendor was later identified as Fireworks AI, a cloud platform for running and fine-tuning open-source AI models. The same credential theft campaign had previously impacted Notion and Cursor. Uber immediately severed the connection upon discovery, notified regulators in multiple U.S. states, and is offering credit monitoring to affected individuals.
Optimizely Supply Chain Attack Infects BBC, CNN, HSBC and 177 Other Sites with Crypto-Stealing JavaScript
On November 16, visitors to major corporate websites received malicious JavaScript that swapped cryptocurrency wallet addresses and attempted to intercept banking card data. The code was distributed through Optimizely Web, a platform used for A/B testing. Researchers identified the malicious code in 188 scripts belonging to 178 organizations, including BBC, CNN, Fox News, HSBC, Equifax, Zoom, Salesforce, GitLab and IKEA. Attacker Scott Helm from Report URI reconstructed the attack timeline: adversaries modified the Project JavaScript field in client projects to load a file from an external domain while legitimate code continued to arrive from cdn.optimizely.com. The campaign began at 04:21 UTC on the BBC script and saw 26 payload updates throughout the day, including a card-data harvesting module added at 13:43 UTC. The malicious script could not access Stripe or Adyen payment forms inside iframes but attempted iOS exploit chains Coruna and DarkSword on affected devices. Optimizely confirmed the breach resulted from a vulnerability in Experimentation account registration, closed the flaw, removed the code and notified customers. Content Security Policy blocked the payload on only 24 of 256 tested sites, and attackers collected roughly $7,040 in cryptocurrency before cleanup completed around 21:52 UTC.
Rspamd 4.3.0 Released with Improved Phishing Detection, Attachment Scanning and Authentication Hardening
In mid-November 2026, developer Vsevolod Stakhov released Rspamd 4.3.0, the latest version of the open-source spam filtering system written in C, C++ and Lua under the Apache 2.0 license. The update strengthens HTTP connection handling, URL-based phishing checks, SPF/DKIM/ARC authentication validation and SMTPUTF8 address parsing while adding more robust attachment and HTML analysis. Key improvements include separate scoring for displayed versus actual link destinations, stricter rejection of weak DKIM keys and duplicate tags, and better archive filename handling to prevent executable hiding. The release also introduces the HTML_TINY_PIXEL_TRACKER rule to detect tracking beacons and fixes multiple bugs that could cause worker crashes or memory issues after free. Several changes may require configuration adjustments for existing users, particularly around symbol options and stricter authentication policies. Rspamd continues to support high-throughput Milter integration with Postfix and Sendmail while offering an extensive Lua API for custom processing logic.
Anthropic Funds New Security Developer Role at Python Software Foundation Following Sharp Rise in Vulnerabilities
Anthropic has financed a new security position within the Python Software Foundation in response to a marked increase in vulnerabilities and malicious packages affecting the Python ecosystem. Data published by Seth Larson showed a significant spike in reported issues during 2026. Brett Smith has been appointed as Security Developer and will collaborate with Larson, who serves as Security Developer-in-Residence, and Mike Fiedler, the PyPI security engineer. The expanded team will focus on scaling automated quarantine mechanisms in PyPI and streamlining the workflows of the Python Security Response Team. At PyCon US 2026, the team reported handling three to four times more vulnerability disclosures for Python and pip compared with the previous year, alongside a 60 percent increase in malware detections and removals from the repository.