🔍 Read the full analysis: This Week’s Security News For AI: Practical Steps For Teams on ThorstenMeyerAI.com
Get audio and creator gear delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
TL;DR
A security roundup published October 29 highlights six developments affecting business networks, phones, email and vulnerability triage. Reported issues include active attacks against Fortinet firewalls, an Android banking crime kit, a malicious PDF backdoor and a fixed Microsoft Authenticator flaw. The practical steps include patching exposed systems, reviewing credentials and treating AI-bot identity claims with skepticism.
Thorsten Meyer published a six-story security roundup on October 29, drawing on advisories and research reports to recommend immediate steps for businesses and everyday users. The selected developments include an active campaign targeting Fortinet firewalls, Android malware designed to steal banking credentials, a backdoor delivered through a disguised PDF, and a Microsoft Authenticator flaw that the company says it has fixed.
The roundup narrows a weekly Hacker News digest of 30 stories to six it considers most relevant. Its main operational warning concerns Fortinet devices: the FBI and U.S. Secret Service said on October 6 that the FortiBleed credential-theft campaign remains active. The agencies cite security firm SOCRadar, which reported verifying more than 86,644 compromised devices in 194 countries. That figure is the firm’s reported count, not an independently established total in the material provided.
The campaign described in the article relies on reused or weak passwords, rather than a newly disclosed Fortinet vulnerability. Attackers may use stolen credentials or crack older password hashes, then add administrator accounts or lock out legitimate staff. Separately, Fortinet issued security updates for FortiOS, FortiManager and FortiAnalyzer on October 22, including critical- and high-severity fixes. The public advisories were scheduled for November 10, according to the source. The two developments should not be conflated: the active campaign and the newly issued software fixes are distinct concerns.
Other selected items include CloudSEK’s October 28 report on MR ROBOT, an Android crime kit rented by criminals to create fake banking apps that can steal one-time codes and forward calls. Trellix reported on October 26 that an empty PDF disguised as a FedEx tax invoice could deliver a backdoor if a user accepted a PDF reader’s warning. Researchers also described an Android Microsoft Authenticator issue that could expose work-account login tokens to another app; Microsoft has fixed the flaw, identified as CVE-2026-80097. Cequence reported a scanner rotating among roughly 32 fake AI-bot identities while seeking password files and cloud keys. Finally, the roundup notes that CISA’s Known Exploited Vulnerabilities catalog is not an exhaustive list of every serious risk: a critical Gotenberg flaw was not listed, despite VulnCheck reporting 1,358 attack attempts over 30 days.
Infographic 01 · Six stories, six actions
This week in security, in one screen.
Six stories that matter for companies and users, each with the one thing to do. Company figures are the researchers' own counts.
The firewall's own backup file
FortiBleed is still active, says the FBI. Hudson Rock counted 40,573 records with plain-text passwords in 1,703 firewall reports. Fortinet shipped critical fixes on 22 October.
The one actionPatch, take admin logins off the internet, reset VPN and admin passwords.
Bank fraud for rent
MR ROBOT: a rented kit that builds fake bank apps, reads one-time codes and forwards calls. One affiliate: 153 devices, 5,407 texts (CloudSEK’s count).
The one actionNever install a bank app from a link in a message.
The blank invoice
An empty PDF posing as a FedEx tax invoice started a hidden command, but only after the victim approved the PDF reader’s warning.
The one actionIf a PDF asks to launch something, click no.
“I'm Teams,” said the app
An app with zero permissions got work-account tokens from Microsoft Authenticator on Android. Fixed as CVE-2026-80097.
The one actionUpdate Authenticator; enforce a minimum version.
32 fake AI bots
One scanner rotated through about 32 AI-bot names while asking for .env files, cloud keys and SSH keys (Cequence’s count).
The one actionNever serve secret files; verify bots by address, not name.
The list is a floor
PHP2Shell is on CISA’s list. Gotenberg, with 1,358 recorded exploitation events in 30 days (VulnCheck), is not.
The one actionPatch the KEV list first, then exploited and internet-facing.
None of this needed magic. Each attack borrowed trust: a stolen password, a click, a name, a text message.Thorsten Meyer · my reading
Sources: Fortinet, 21 Oct 2026 · FBI and USSS, 6 Oct 2026 · Hudson Rock, 27 Oct 2026 · CloudSEK, 28 Oct 2026 · Trellix, 26 Oct 2026 · Enclave, 23 Oct 2026 · Microsoft, CVE-2026-80097 · Cequence, 28 Oct 2026 · CISA KEV, catalog 2026.10.28 · VulnCheck, 26 Oct 2026. Selection and wording: Thorsten Meyer.
Powered by Thorsten Meyer AI
Prioritize Firewalls and Credentials
The reports point to practical exposure across several parts of an organization’s security perimeter. Internet-facing firewalls can be compromised through credential failures even when the issue is not a new software bug. A stolen or weak password may give an attacker a foothold with broad access, while configuration backups can contain sensitive account information.
For security teams, the Microsoft Authenticator case also shows why patch status and app permissions deserve review: a flaw affecting a trusted authentication app can put work-account tokens at risk. For individual users, the fake banking apps and invoice-themed PDF demonstrate how criminals can use familiar brands and routine prompts to persuade people to grant access or dismiss a warning. The AI-bot report adds a related caution: a user-agent label or claimed identity is not proof that a web request comes from a legitimate AI service.
The roundup’s central value is its focus on actions rather than a threat count. Teams can review firewall exposure, rotate credentials, require multifactor authentication, apply vendor updates and inspect logging. These measures address the specific methods described without assuming every report represents a confirmed compromise at a reader’s organization.
Products Worth Considering

Apple AirPods Pro (2nd Generation) Wireless Earbuds with USB-C MagSafe Charging Case

Bose QuietComfort True Wireless Earbuds with Active Noise Cancellation, Bluetooth 5.3, USB-C Charging, IPX4, Black

DJI Mini 4K Camera Drone Combo with 2 Batteries
As an affiliate, we earn on qualifying purchases.
Six Reports Behind the Roundup
The source article says it selected six items from The Hacker News’ October 29 weekly digest and returned to original advisories or research reports where available. It identifies the sources as Fortinet, the FBI and U.S. Secret Service, CloudSEK, Trellix, Enclave, Microsoft, Cequence, CISA and VulnCheck. Several quantitative findings come from cybersecurity firms that also sell security products; the article says it labels company-generated counts and urges readers to retain their stated scope.
For FortiBleed, the roundup distinguishes the campaign from Fortinet’s October 22 security updates. The agencies’ October 6 warning concerns ongoing exploitation involving credentials, while the vendor’s updates address software vulnerabilities. Fortinet said the campaign was not a new Fortinet vulnerability and attributed access to credential reuse, password guessing and weak passwords without a second factor. The public advisory details for the October updates were due November 10, leaving the specific vulnerability information unavailable in the source material.
The article also compares CISA’s KEV catalog with reporting on Gotenberg, a document-conversion tool. CISA gave U.S. federal agencies three days to address PHP2Shell, while VulnCheck reported 1,358 attempts against the Gotenberg flaw in a 30-day period. Those figures describe different items and sources; the roundup does not establish that the Gotenberg attempts succeeded or that every organization using the tool is exposed.
“FortiBleed “is not a new Fortinet vulnerability”.”
— Fortinet, as quoted in its PSIRT statement cited by the roundup
Counts and Exposure Still Unclear
The figures in the reports do not establish the number of victims currently at risk. SOCRadar’s 86,644 figure is described as verified compromised devices, while Hudson Rock’s October 27 analysis covered 1,703 configuration reports from 1,689 devices and identified 40,573 password-containing records. Hudson Rock said those were records, not people, and noted that 7,437 local accounts were marked disabled. The roundup does not establish how many accounts remain usable or how many affected systems are still compromised.
Details of Fortinet’s October updates were not yet public in the source material: the vendor’s advisories were scheduled for November 10. The exact scope of the Authenticator flaw and the full remediation guidance are also not detailed here, beyond the report that Microsoft fixed it. For the Gotenberg finding, the reported 1,358 attempts do not show how many were successful, who was targeted or whether CISA would later add the issue to its catalog.
The six selected reports are a curated sample, not a complete account of the week’s threats. The source material also does not verify that every reported campaign or vulnerability affects a particular reader’s systems. Teams need to compare vendor notices and their own inventory, logs and configuration data before drawing conclusions about exposure.
Patch, Review, and Verify
Organizations using Fortinet products should identify internet-facing devices, apply the October updates relevant to their versions and follow Fortinet’s advisories when they are published. Security teams should also review administrator accounts, remove unneeded access, replace reused credentials, require multifactor authentication and check whether configuration backups contain exposed passwords. If a device may have been compromised, teams should investigate account changes and access logs rather than treating a software update alone as proof that an intrusion has been resolved.
Users and IT administrators should confirm that Microsoft Authenticator is updated, install legitimate banking apps only from trusted sources, and decline unexpected requests to approve access or dismiss document-security warnings. Security teams can add the reported Gotenberg issue to their own review even though it was not in CISA’s KEV catalog at the time described, and verify exposure against the tool’s vendor guidance.
The next dated milestone identified in the source is November 10, when Fortinet’s public advisories were expected. Until then, affected organizations must rely on available vendor update information and their own asset inventories. The roundup does not state a later update date for the other reports.
Key Questions
What is FortiBleed?
FortiBleed is the name used in the roundup for a campaign targeting Fortinet firewalls with credentials, including reused or weak passwords. The FBI and U.S. Secret Service said the activity was ongoing in an October 6 warning; Fortinet said it was not a new Fortinet vulnerability.
What should organizations do about Fortinet devices?
Identify affected FortiOS, FortiManager and FortiAnalyzer systems, apply the relevant vendor updates, and monitor Fortinet’s advisories. Review administrator accounts, change reused or weak passwords, require multifactor authentication and investigate suspicious account changes.
Has Microsoft fixed the Authenticator issue?
The source article says Microsoft has fixed the Android flaw, identified as CVE-2026-80097. It does not specify the full affected-version range or detailed remediation steps, so administrators should consult Microsoft’s current guidance and confirm that devices are updated.
Does the Gotenberg attack count mean systems were breached?
No. VulnCheck reported 1,358 attack attempts over 30 days, but the roundup does not say how many succeeded. Organizations should check whether they use an affected version and follow vendor guidance rather than treating the attempt count as a confirmed victim total.
Why does the roundup say CISA’s list is not enough?
The roundup cites Gotenberg as a critical flaw that was not on CISA’s Known Exploited Vulnerabilities catalog at the time, despite VulnCheck’s report of attack attempts. The point is that teams should also review vendor advisories and their own risk assessments; the catalog is not presented as a complete list of every relevant vulnerability.
Source: ThorstenMeyerAI.com
