Expanded and checked on 23 October 2026. This guide now addresses all 17 entries visible in the circulating list we reviewed. Sixteen have supporting primary evidence; the State Bank of India entry remains pending verification of its exchange filing. Vendor investigations and advice can change.
“Black October” is an informal label appearing in discussion about cybersecurity headlines. For an Eswatini business, the useful question is what to check before a problem interrupts bookings, payments, customer enquiries or everyday work.
The reports cover different products, affected groups and dates. Some describe newly disclosed vulnerabilities; others concern attacks that started months earlier. Treat the dates and scope as part of each story, rather than assuming every event happened this month or affects your business.
For the separate urgent PHP issue, start with our PHP2Shell guide: fixed versions, a message for your host and checks after an update.
The 17 reports, checked individually
Find the products and services you use. The questions below are starting points for your provider or administrator; they are not evidence that your own system has been breached.
- Signal
- NGINX
- HTTP/3 and QPACK
- Plex
- SafePay ransomware
- Palo Alto Networks
- Bullhorn
- Medi-Cal / Paradigm Healthcare
- WordPress / TeamUpdraft
- AOMEI
- Meta Muse
- Tor exit relays
- TiDB Cloud / PingCAP
- State Bank of India
- OVHcloud CLI
- Siemens Software Center
- North Korea / Operation FlashHole
Signal
The 20 October CVE record says a participant in an existing call could disrupt hang-up processing in RingRTC before 2.72.0, allowing audio and possibly video to continue. Read the primary source.
What to check: Update Signal on every device through its official update channel. The vulnerable library version is not the app version number.
Keep the scope clear: The record describes possible video exposure; it does not establish arbitrary microphone activation outside a call.
NGINX
NGINX lists request-processing and TLS-session advisories with specific affected versions and configurations. The current entries do not support describing every listed issue as critical. Read the primary source.
What to check: Ask your host which advisories apply to its NGINX build and configuration, and obtain confirmation of the relevant updates.
Keep the scope clear: Do not repeat the screenshot's three-critical-holes or one-third-of-websites exposure claim.
HTTP/3 and QPACK
FoxIO's 20 October research found memory-exhaustion problems in seven of ten tested implementations. Some fixes were available; other implementations needed mitigations. Read the primary source.
What to check: Have your host identify its HTTP/3 implementation and follow the current vendor fix or configuration guidance.
Keep the scope clear: Seven of ten tested implementations is not 70% of all websites. This research describes denial of service, not proof of stolen data.
Plex
Plex's 19 October update reports attacks against unpatched internet-facing servers. Its earlier notice identified fixes in Media Server 1.43.3 and Desktop 1.115.0. Read the primary source.
What to check: Check the actual server and desktop versions, including NAS installations. Apply current official updates and investigate suspicious activity.
Keep the scope clear: The update notice began in September; this is not proof every Plex user has been compromised.
SafePay ransomware
The 20 October joint advisory reports at least 600 victims across multiple critical-infrastructure sectors. Its account covers activity since August 2024. Read the primary source.
What to check: Prioritise exposed VPN and firewall updates, account protection, restricted administrator access and a tested recovery plan.
Keep the scope clear: The 600 figure is cumulative, not an October-only incident count.
Palo Alto Networks
Unit 42's October update reports ransomware operators attempting to exploit CVE-2026-0257, a PAN-OS authentication-bypass issue affecting applicable GlobalProtect deployments. Read the primary source.
What to check: Have the firewall administrator check the vendor advisory, patch status and relevant access logs. Review any suspicious VPN activity.
Keep the scope clear: Applicability depends on version and configuration; a firewall brand alone does not establish exposure.
Bullhorn
Bullhorn's 21 October update distinguishes its contained 17 October cyber incident, precautionary PHP-related service shutdowns and a separate account-change replication problem. Read the primary source.
What to check: Check the status of the specific product you use, follow vendor account instructions and keep an agreed continuity process.
Keep the scope clear: Do not merge three separate events into one attack or describe every product as currently offline.
Medi-Cal / Paradigm Healthcare
Paradigm confirms a network incident discovered in October 2025. It identified possible access to selected health-information files in August 2026; its online billing platform was unaffected. Read the primary source.
What to check: Affected people should use the provider's notice. Businesses should review what customer information suppliers retain and how incident notices reach them.
Keep the scope clear: The vendor notice read here does not establish the screenshot's 970,000 figure. Do not present this as an attack that began in October 2026.
WordPress / TeamUpdraft
TeamUpdraft reports stolen service connection keys and unauthorised access to customer sites. Its notice distinguishes affected hosted services from unaffected self-hosted UpdraftCentral and uncompromised plugin downloads. Read the primary source.
What to check: Follow the instructions for your exact product, revoke or re-establish affected connections as directed, and investigate unexpected accounts or plugins.
Keep the scope clear: This is not evidence that every WordPress site or every UpdraftPlus download was compromised.
AOMEI
Google Threat Intelligence Group and Mandiant documented brief update-configuration tampering that delivered malicious software. The described activity occurred in May and July 2026. Read the primary source.
What to check: If you used the relevant software, ask IT to compare installation history with the research and assess any affected device.
Keep the scope clear: An October report date is not an October attack date. Avoid implying every AOMEI update was malicious.
Meta Muse
Claroc found discoverable public conversation-share links exposing sensitive material. Its 20 October update says Meta paused sharing and previously accessible samples no longer opened. Read the primary source.
What to check: Review AI conversation shares and connected permissions. Remove unnecessary public links and assess any secrets included in shared content.
Keep the scope clear: The finding concerns published shares; it does not show that every private Muse conversation was exposed.
Tor exit relays
Researcher KABA reported 333 exit relays involved in SSH redirection in early October. The Tor Project confirmed affected relays were being flagged and rejected. Read the primary source.
What to check: Do not dismiss changed SSH host-key warnings. Administrators should verify keys independently and investigate credentials used through suspicious connections.
Keep the scope clear: This is a specific relay and connection incident, not evidence that every Tor user's passwords were stolen.
TiDB Cloud / PingCAP
PingCAP reports stolen credentials used between 9 September and 7 October to copy internal records. It says there is no evidence that data stored in customer TiDB databases was impacted. Read the primary source.
What to check: Follow PingCAP's precautionary management-API-key rotation instructions and be alert to targeted phishing while customer-specific impact is investigated.
Keep the scope clear: Internal account, billing and SQL-editor records are distinct from proof of access to every customer database.
State Bank of India
Verification pending. We identified the bank’s exchange filing but have not verified its contents. We are holding the circulating impact figures and claims about core banking access until that check is complete. Identified exchange filing.
What to check: Use a known bank channel to check notices and verify messages. Do not treat knowledge of your personal details as proof a caller is legitimate.
OVHcloud CLI
OVHcloud confirms malicious replacement release files for versions 0.11.0–0.15.0 during 14:47–16:21 UTC+2 on 19 October. Earlier downloads and the source/build chain were unaffected; 0.16.0 was unaffected. Read the primary source.
What to check: Check download and execution history against the advisory. If affected, involve IT in device investigation and credential recovery; updating alone does not establish cleanup.
Keep the scope clear: This concerns particular downloaded CLI files, not every OVHcloud-hosted website.
Siemens Software Center
The official alert confirms exploitation of CVE-2026-110936 before version 4.0.9.8. Attackers paired a legitimate signed application with malicious DLL files; Siemens reported no breach of its update channels. Read the primary source.
What to check: Update affected installations and investigate unexpected software. Do not run unsolicited commands or downloads presented as a security fix.
Keep the scope clear: A legitimate signed application being abused is different from Siemens' official update channel being compromised.
North Korea / Operation FlashHole
Kaspersky attributes Operation FlashHole to Lazarus and identifies targeted South Korean organisations. Its earliest evidence dates to July 2025, with tailored phishing and abuse of legitimate software. Read the primary source.
What to check: Verify unexpected recruitment or business links through a known contact, keep relevant software updated and give staff a clear way to report concerns.
Keep the scope clear: This does not establish an October-only campaign or that businesses in Eswatini are its documented targets.
Five checks to put into practice
1. Ask for patch evidence, not a general reassurance
Write down the systems that keep the business moving: website, hosting, email, remote access, firewall, accounting, bookings and backups. Put a responsible person or supplier next to each one. Ask them to check applicable vendor advisories and record the installed build, action taken and outstanding work.
For PHP, our detailed guide includes the two CVE identifiers, first fixed versions and a message you can forward to your host. It also explains why an up-to-date WordPress dashboard is not enough to confirm the hosting runtime is patched.
2. Review the connections you trust
Ask who can administer the website remotely and which external services retain access. Include maintenance dashboards, backup tools and old supplier accounts. Remove access that is no longer needed through the normal authorised process.
Where a vendor reports stolen connection keys, follow its key-revocation and reconnection instructions. Treat unexpected accounts or plugins as an investigation issue. Keep screenshots, timestamps and logs for the responder rather than assuming that deleting one unfamiliar item completes recovery.
3. Protect the accounts that control the rest
Start with the primary business email account, domain registrar, hosting panel and backup administrator. Use unique passwords stored in a reputable password manager and enable multifactor authentication where available. Review recovery details and ensure the business can regain access if the usual administrator is unavailable. These align with CISA’s basic protection guidance. CISA: Secure Our World.
Give staff a trusted way to verify urgent update or payment messages. Visit the vendor through a known address rather than following a frightening advert or an unexpected “security fix” link. A real security story can also be used as bait.
4. Find out whether you can restore
Ask your IT provider to demonstrate a restore of an agreed, non-production sample and record the result. Confirm which data is covered, how old a usable copy could be, and who controls access to it. Keep backup access appropriately separated from everyday accounts.
A “backup successful” notification is useful, but a recorded restore gives you evidence about recovery. Agree which service must return first if the business is interrupted, and how customers will contact you while that happens.
5. Make the first response clear
Put the hosting provider, IT support contact and business decision-maker in one short response sheet. If staff see an unexpected login, changed payment details, unusual administrator account or suspicious program, they should know whom to contact and what information to retain.
Have your IT responder direct containment and evidence preservation. Avoid improvised wipes or recovery changes that can destroy useful evidence. A suspected compromise needs a different scope from a routine patching job.
Use this action record in your next team check-in
| Action | Evidence to request |
|---|---|
| Critical patch review | Applicable advisory, running build, completion date and unresolved items |
| Trusted-access review | Current administrator and service connections; unnecessary access removed |
| Account protection | MFA enabled, recovery process checked and responsible owner identified |
| Restore check | Agreed sample restored, date, result and recovery gaps |
| Response readiness | Current contact sheet and a person authorised to make containment decisions |
For each row, add your owner, target date and status: confirmed, action required or still unverified. “Still unverified” is a useful result when it leads to a named next step.
Awareness should leave you with a next step
October’s international Cybersecurity Awareness Month is an opportunity to put useful habits into practice. We are sharing these checks to help businesses in Eswatini turn awareness into action. National Cybersecurity Alliance: the October 2026 campaign.
If you need help deciding what applies to your business, ask BusiQuip for a scoped cybersecurity review or request a quote on WhatsApp at +268 7878 0709. Agree the work and fee first. The goal is fewer unresolved risks and a clearer recovery plan; no single service can guarantee protection against every attack.
Continue with the PHP2Shell update guide, explore BusiQuip’s cybersecurity services, or browse our other business guides.






