Festive Skills Fest:
 BUY 1 Course GET 1 FREE Limited-Time Offer

CyberWatch Daily: FBI Clarifies Its ARTEX Advisory, Optimizely Flaw Hits 178 Organisations’ Websites

The FBI has clarified its ARTEX advisory after a field office post spread it widely during this week’s US outage panic. In a separate development, a flaw in Optimizely turned the websites of 178 organisations into malware delivery for most of Monday. Here’s a closer look at today’s major cybersecurity headlines.

FBI Clarifies Its ARTEX Advisory After a Field Office Post Met the Outage Panic

The ARTEX advisory went out on Friday 13 November. On Tuesday the bureau’s Dallas field office posted it on X. It spread quickly, against a backdrop of outages at Microsoft, JPMorgan Chase, the FAA and the NSA’s internal network.

The bureau then clarified that the advisory “is not a new announcement”, that no further warning has been issued since, and that the guidance remains current. According to an FBI official, ARTEX does not appear connected to the NSA network trouble, JPMorgan’s banking outage, reported malware attacks involving Optimizely, the FAA ground stop or the Microsoft Outlook disruption.

The substance did not change. The FBI says malicious actors have used ARTEX since at least August against organisations in financial services, government, technology, defence, semiconductor, energy, healthcare, manufacturing, telecommunications and legal work. The alert says the framework “significantly reduces the time required to chain attack techniques”. Some intrusions reached privileged access in under three hours.

The advice has not changed either. Review what you have facing the internet, keep administrative tools to the people who need them, and watch for sign-ins and data transfers that look out of place. The developer took the public repository down in October once the misuse came to light. However, copies and modified versions are still out there.

Sources: FBI, Infosecurity Magazine, ABC News

Optimizely Flaw Turned the Websites of 178 Organisations Into Malware Delivery

An attacker exploited a flaw in Optimizely Web Experimentation on 16 November and wrote a loader into the Project JavaScript field of customer projects. That field is served inside the vendor snippet from Optimizely’s CDN, so the code reached visitors from the vendor’s own domain under its own certificate. Optimizely says the entry point was its account signup flow.

Scott Helme of Report URI checked 1,611 Optimizely snippets and found the code in 188 of them, belonging to 178 organisations. Affected organisations include the BBC, CNN, Zoom, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM and Peacock. Optimizely’s own website and login page carried it too.

The payload changed cryptocurrency addresses across eight chains through clipboard manipulation. On pages where it replaced an address, it also sent accessible cookies and a screenshot to the attacker. A card skimmer added at 13:43 UTC read card numbers, expiry dates and security codes from site hosted forms. iOS exploit kits followed, aimed at iPhones on iOS 18.6 or earlier. However, Cynet called this conditional delivery rather than confirmed compromise.

Report URI first detected the injection at 04:21 UTC, with mass cleanup beginning around 20:40 UTC. Optimizely’s official incident report gives the exposure window as 07:51 to 22:24 UTC.

Helme’s running total reached about $7,040. However, two wallets were in use before the campaign, and the chain does not show which transfers came from victims. How much card data was taken is anyone’s guess. Blocking the domain will not close this: one version of the loader carries the whole payload inline, so it keeps working even when the domain is gone. The code has to come out of the project.

Sources: Infosecurity Magazine, Help Net Security, Security Affairs, The Register 

Conclusion

Both stories ask the reader to judge something they did not build. One is a federal advisory that held up while the story around it did not. The other is a vendor script that 178 organisations had already chosen to trust.

Neither is settled by auditing your own code. Instead, both turn on how much trust to place in something built elsewhere.

 

TOP