The Pratidhwani

FBI warns companies in the US and across the world; names AI hacking tool criminals are using to attack financial services; suggests dos and don’ts


FBI warns companies in the US and across the world; names AI hacking tool criminals are using to attack financial services; suggests dos and don'ts

Hackers are increasingly deploying autonomous artificial intelligence tools to execute high-speed cyberattacks across the United States and around the globe, according to a flash cybersecurity advisory issued by the Federal Bureau of Investigation. The warning highlights a wave of recent intrusions targeting major sectors—including government, defense, telecommunications, law, technology, and finance—with major fallout already documented across South Korea’s financial industry and among thousands of customers of American IT firm ConnectWise.At the center of the FBI’s alert is Artex, an open-source, AI-powered penetration testing platform originally designed to probe network defenses. By linking Artex to frontier large language models from companies like OpenAI and Anthropic, as well as open-source and foreign AI models, threat actors have been able to automate the discovery and exploitation of basic security flaws. “Since at least August 2026, a variety of malicious cyber actors have used Artex to conduct campaigns targeting organizations globally across multiple sectors, including financial services, government, technology, defense, semiconductor, energy, healthcare, manufacturing, telecommunications, and legal industries,” said FBI in its report.While federal officials noted that Artex-driven intrusions are often “noisy”—generating high volumes of network traffic that can set off security alarms—the software operates at a pace that routinely outstrips human response times. In several observed cases, attackers progressed from initial targeting to full system compromise in under three hours.Once aimed at a target, the software rapidly scans networks for low-hanging vulnerabilities, such as weak configurations, missing multi-factor authentication, or exposed passwords. Upon securing a foothold, the tool autonomously navigates internal systems to harvest sensitive databases, mailboxes, and credentials.Since Artex debuted publicly in July, its capabilities have been tied to several high-profile breaches. In South Korea, attackers leveraged the platform against multiple financial institutions lacking basic protections like multi-factor authentication, resulting in the theft of personal records belonging to at least 68,000 individuals. “As of early November 2026, researchers identified over 1,600 publicly exposed ARTEX console instances, with total deployments likely significantly higher when including systems behind firewalls or in private networks,” says FBI.The FBI also corroborated earlier intelligence from Microsoft detailing how threat actors—believed by Microsoft to be operating out of China—used Artex to infiltrate IT management provider ConnectWise. Through that breach, the hackers accessed the Microsoft 365 cloud environments of at least 2,250 ConnectWise customers to exfiltrate data.Although the creator of Artex has since transitioned the software to a closed-source model in an effort to curb abuse, the FBI cautioned that earlier open-source versions remain widely circulated and easily accessible online. Compounding the threat, careless operational security by the hackers themselves has left hundreds of active Artex instances exposed on the public internet without password protection. Just last week, cybersecurity researchers discovered numerous unprotected deployments online—including the exact system used to orchestrate the attacks against South Korea—potentially leaving powerful, turnkey hacking infrastructure open to anyone who stumbles across it.

FBI recommends organizations take the steps below to improve their security posture:

• Restrict cloud administration, network device management, application publishing interfaces (Kudu/SCM endpoints), hypervisors, backup platforms, and other sensitive services to trusted networks,private connectivity, or dedicated administrative paths.• Disable basic publishing authentication where not required; restrict access to deployment and publishing credentials; restrict SCM access to approved management networks or deployment infrastructure.• Consider deployment models such as run-from-package that reduce direct modification of deployedapplication files.• Establish governance around public IP allocation; require architecture review before workloads or management interfaces are exposed directly to the internet.• Move enterprise applications behind Zero Trust access solutions to eliminate external exposure where feasible.* Put guardrails around high-impact business APIs: rate limits, recipient limits, transaction thresholds, abuse controls appropriate to function; alert when application operates materially outside normal volume.* On partner and employee portals, alert on sequential lookups and unusually high numbers of records accessed per session; apply rate limits to affected endpoints; enforce server-side authorization for access to customer records and limit responses to fields required for the operation.



Source link

Exit mobile version