BFSI Cyber Threat Intelligence · Tuesday Edition

Tuesday BFSI Cyber Threat Briefing

New reports that affect banks, financial services and insurers. Each item says what is confirmed, what is disputed, and what is still unknown. Claims are not treated as facts.

Window: 2 Nov ~10:45 SGT → 3 Nov 2026, 10:45 SGT (24 hours) Published: Tuesday 3 November 2026 Dedup: Monday edition (30 Oct – 2 Nov) items appear only as status updates
Ivanti CVE-2026-111357 · deadline 2 Nov
Passed

No new victim, exploit code, or completion statement was found in this window. That is not proof that all systems are safe. The second CVE in the chain is due 13 Nov.

Siemens CVE-2026-110936 · deadline
Due today, 3 Nov

No proof of completed fixes was found in this window. No proof is not proof of failure. It is a gap to close today. Confirm Software Center ≥ V4.0.9.8.

Binance proof-of-reserves
Still pending

The full zero-knowledge proof was due “by Tuesday 3 Nov (UTC)”. The UTC day had not ended at the 10:45 SGT cutoff. Only the 31 Oct snapshot was public. Critique: even when it arrives, a proof of reserves shows holdings on one date. It does not show what the exchange owes.

Google Android November bulletin
Published 2 Nov

216 fixes, 23 critical. No exploitation was flagged. That means none was reported in the bulletin. It does not prove none occurred. See the watchlist below.

Executive summary

1

Mercado Bitcoin and Binance are the most serious items. They are two separate incidents. Mercado Bitcoin, Brazil's largest exchange, was drained across 17 blockchains in the early hours of 2 Nov. About $10m was frozen. No attacker was named, and how the attacker got in is unknown. Critique: the ~$49m total is a researcher's estimate. The exchange's own figure is about $38m. They measure different things and must not be added together. The exchange's promise of no customer loss is its own claim, not independent proof. Separately, Binance lost about $6.3bn. The FBI blames North Korea's TraderTraitor/Lazarus cluster. North Korea denied this on 3 Nov. Net outflows were $3.64bn. Fake “$150 compensation” scams are using the incident to target customers.

2

Ivanti is the top patch-and-hunt priority. The federal deadline for CVE-2026-111357 passed on 2 Nov. The second deadline, for CVE-2026-118527, is 13 Nov. Siemens CVE-2026-110936 is due today, 3 Nov. Critique: a passed deadline does not mean every system is safe. Patching alone does not answer whether a system was already used. Activity held only in memory may not be seen by Ivanti's Integrity Checker. A clean check is therefore not proof that a system was never touched. The risk is direct: these flaws can give an attacker a foothold, then access to identity and credential stores.

3

Vendor risk is the second theme. Abrigo restored Sageworks on 2 Nov. The platform had been shut down after “irregular activity”. More than 2,400 US banks and credit unions were affected. Borrower-facing features were still down. Critique: “irregular activity” does not answer the key question — was data taken, or not? The claim against AU Small Finance Bank, via a Salesforce-hosted platform, is also unverified. The bank says core systems are unaffected. CTOS restored credit-reporting services. In each case, the problem sits with a vendor, but the bank must still show what was, and was not, exposed.

No new FIN7, LockBit, RansomHub, Cl0p or bank-focused Initial Access Broker campaign was found in this window. That is a limit of what was published and searched. It is not evidence that those groups were inactive. “Confirmed exploitation” below means a CISA KEV listing, a vendor confirmation, or a named incident-response account. It does not mean a leak-site claim or an aggregator's assertion. A leak-site listing date is not a compromise date.

Threat actor activity

Who is claimed to have acted, who was targeted, how, and with what effect. MITRE ATT&CK labels are shown only where a source published them. Analyst mappings and unverified claims are labelled as such, and each card notes what the claim does not prove.

Status updateState-sponsored

TraderTraitor / Lazarus Group (North Korea)

Crypto exchange · Global — Binance (Binance.com; US platform said unaffected)

TTPs
Access may have started with a compromised DevOps engineer's laptop. It then reached a service container, and unauthorised withdrawals followed. This is an analyst mapping (T1078 Valid Accounts / T1566 Phishing). Binance has not finally confirmed how access began. It later said “additional points of breach” were found. Funds were converted mostly to ETH, then moved through DeFi and instant-swap services (T1020 / T1496-adjacent, per FBI via Help Net Security). The FBI listed 628 addresses to block: 608 ETH, 19 BTC, 1 SOL.
Impact
About $6.3bn was stolen on 29 Oct. Reporting calls it the largest crypto theft on record. About $3bn was frozen on the first day (Tether/Circle et al.). Binance says about 95% of stolen assets were replaced from its treasury, futures insurance and emergency reserves. Net outflow was $3.64bn in 9.5 hours on 1 Nov ($4.649bn out / $1.01bn in; 2.1% of $171bn AUM, per Binance). On 3 Nov, North Korea denied involvement via Kim Yo-jong (“absurd rhetoric” / “trite provocation”). Critique: a denial does not disprove the FBI attribution. The attribution does not make it certain either. The full evidence is not public. The outflow and replacement figures also come from Binance itself. They are useful, but they are not audited.
New in windowNo attribution published

Unknown actor — Mercado Bitcoin incident

Crypto exchange · Brazil

TTPs
Funds were drained “in waves” across 17 blockchains. The largest tranches were BTC and ETH, plus Base, Tron and Polygon. No entry method was published. Do not assume phishing, malware, or abuse of valid access.
Impact
About $49m was stolen early on 2 Nov (Chainalysis estimate). The exchange gives different figures: about $38m in “assets involved” and $11m blocked. The two methods must not be added together. About $10m was frozen (over $9m USDT via Tether, plus Paxos / Anchorage / Ripple / Circle coordination). Services were suspended, with no reopening time given. Critique: what is not known matters more here. We do not know how the attacker got in, who they were, or whether customers lost money. The promise of no customer loss is the exchange's own claim.
New leak listingUnverified claim

Akira — ransomware, double extortion

Financial services · United States — Princeton Management

TTPs
Double extortion: data is taken, then encrypted, then published on a leak site (T1567 Exfiltration / T1486 Data Encrypted for Impact). That is the standard Akira model, per the source. It is not confirmed by the victim in this case. Note the classification problem: Princeton Management is a property-management firm in the leak post. The tracking site classifies it as financial services.
Impact
A leak post dated 2 Nov 2026 claims 130 GB “will be uploaded soon”. It lists employee PII (phones, addresses, scans, military-veteran information), contracts, client and partner information, financial records, specs and drawings. Critique: a leak-site listing is a claim, not proof of a breach. No ransom amount, no compromise date, and no victim confirmation were found.
New leak listingUnverified claim

Pear / PEAR Team — ransomware, double extortion

Financial services · United States — Neiman & Company, Inc.

TTPs
Double extortion (T1567 / T1486). That is the standard model, per the source. It is not confirmed for this victim.
Impact
The leak listing is dated 2 Nov 2026. The tracker attributes 137 victims to the group. Critique: that total comes from the tracker. It is not proof in this case. The data said to be stolen was not independently verified. No compromise date or victim confirmation was found.
Leak published in windowIncident is older

Settra — ransomware

Financial services · United Kingdom — Kingdom Title (kingdomtitle.net)

TTPs
Data theft is the main extortion tactic (T1567). The attack route is not confirmed by the source.
Impact
The leak was published on 2 Nov 2026. The incident is estimated at 8 Oct 2026. Critique: the two dates must not be mixed. Publication is not the date of compromise. The leak summary shows an incoming book transfer of $15,319,440, an outgoing wire of $14,947,415, trial balances totalling $1,277,500.31 (2,972 positive balances), personal auto, umbrella and boat insurance policies, and payment notes. These figures come from the leak summary. They were not confirmed by the victim in the sources found.
Follow-up in windowEdge / VPN chain

UTA0576 — Ivanti Connect Secure chain

Edge/VPN users, incl. financial firms on Ivanti Connect Secure · Global

TTPs
Three flaws are chained to reach unauthenticated root: CVE-2026-104935 (auth bypass / RCE), CVE-2026-118527 (predictable upload) and CVE-2026-111357 (privilege escalation). Credentials are then stolen. Active Directory is queried for Windows LAPS passwords and BitLocker recovery keys (T1003 OS Credential Dumping / T1555 Credentials from Password Stores — an analyst mapping of the reported behaviour). This is not FIN7 or Scattered Spider.
Impact
Ivanti says the impact is “limited to a small number of customers” (via HOL). Critique: that phrase is the vendor's. It does not name the customers or the data taken. CISA lists ransomware use as unknown. No public exploit code is cited in the advisories. The risk is a foothold plus theft from identity stores. There is no confirmed BFSI victim in this window.
Claim onlyUnverified

ScarlettGroup — claim against AU Small Finance Bank

Banking · India — via a Salesforce-hosted SaaS platform (vehicle-loan customers)

TTPs
Claim only. The method is not established. The data said to be taken: KYC, PAN/Aadhaar, bank statements, credit reports / CIBIL, loan agreements, CRM data, and employee audit logs.
Impact
The bank said on 2 Nov that it is investigating. It says core systems are unaffected and services are normal. Salesforce said (Saturday) it found no flaw at its end. Critique: those statements do not settle the claim. The bank has not said no data was taken. Salesforce has not said where the data came from. The number affected, and whether the Salesforce platform is the source, are not confirmed. Treat this as an unverified claim, not a confirmed breach.
Allegation onlySupply chain

ShinyHunters — allegation via Abrigo history

Fintech · US banks & credit unions — Abrigo

TTPs
Allegation only: an earlier claim that 1.7m Salesforce records were taken from Abrigo (names, emails, phones, employee and account data). No link has been established to the current Sageworks outage. The two must not be merged.
Impact
There is no confirmed breach for the old claim or for the current outage. Critique: no confirmation is not the same as proof that nothing happened. Researchers advise rotating Sageworks API keys as a precaution.
Reported in windowMule accounts

Unnamed fraud syndicate — Assam STF arrests

Banking · India — mule accounts, incl. an SBI account

TTPs
Mule-account laundering. Money moved in and out quickly over 47 days (22 Jun – 5 Aug 2026). The network operated across states for about 2 years (T1078-adjacent account abuse; this is a police account, not a MITRE-mapped campaign).
Impact
Six people were arrested on 28–30 Oct. This was reported on 2 Nov at 21:03 SGT. “Several crores” were allegedly siphoned. Critique: “allegedly” matters. The amounts come from the police account. A suspected Pakistan-intelligence link is under probe only. It is not established.
No new item was found in this window for FIN7 / Carbanak, Scattered Spider, LockBit, RansomHub, Cl0p, or Initial Access Brokers selling bank access. Scattered Spider appears only in a general 2 Nov podcast on helpdesk social engineering and lookalike domains. That is not a new incident. Older reporting (for example, September 2025) was not added back. Critique: absence in search is not proof of inactivity.

Vulnerability watchlist

Fourteen rows from the research report. Scores that disagree are shown as disputed. One listing is unconfirmed and is flagged as such. A high score alone does not mean a flaw is being used. A low score in a chain does not mean low risk. Filter by status, or search by CVE or product.

CVE IDCVSSAffected product Exploitation statusRelevance to finance
CVE-2026-111357 8.8 — disputed: 7.0 in CVETodo (1 Nov); not reconciled in sources Ivanti Connect Secure (25.1.1.2, 22.8R2.5; fixed in 25.1.1.3 / 22.8R2.6) In the wild — CISA KEV 30 Oct, chained with CVE-2026-104935 / 118527; forensic triage required; federal deadline was 2 Nov Edge VPN for remote and bank-branch access. A root foothold, plus theft of AD, LAPS and BitLocker credentials, threatens the identity systems of any financial firm on Connect Secure
CVE-2026-118527 4.3 Ivanti Connect Secure (same builds as above) In the wild (chained) — CISA KEV 30 Oct; authenticated predictable file upload (wu.cgi → /home/runtime/tmp/, MD5 filename, Perl race); federal deadline 13 Nov Same chain as above; the low standalone score understates the chained impact
CVE-2026-104935 8.6 Ivanti Connect Secure (fixed in 13 Oct builds, then superseded) In the wild — auth bypass / RCE at the front of the chain; CISA KEV, federal deadline 16 Oct (passed) Entry point for the Ivanti chain above
CVE-2026-110936 8.4 (CVSS v4.0) / 6.7 (v3.1) — both published, different scoring versions Siemens Software Center (< V4.0.9.8) In the wild — CISA KEV 20 Oct; exploited via the Romulus ClickFix campaign (malicious DLL beside the genuine signed Software Center); federal deadline today, 3 Nov; ransomware use unknown Indirect. This is not a core-banking product. Act first only where Software Center is installed. The wider lesson is the method: a malicious DLL beside a genuine signed tool, delivered by ClickFix. That method can be reused against bank workstations
CVE-2026-97229 10.0 GitLab CE/EE (19.2 <19.2.8, 19.3 <19.3.5, 19.4 <19.4.2) In the wild — CISA KEV; unauthenticated RCE in CI/CD (regex validation); Alpine Linux targeted 20–21 Oct, worker crashes, full rebuild after log gaps DevOps and CI supply chain for fintech and bank engineering teams. A GitLab RCE is a path to code and secrets. It is not only a dev-tool bug
CVE-2026-76418 8.6 Cisco Secure Firewall ASA / FTD In the wild — CISA KEV 29 Oct (per VECTR-CAST); unchecked return value → NULL dereference, unauthenticated remote DoS (restart) Edge firewall availability for branches, payment and VPN paths; DoS-only, not RCE, per reporting
CVE-2026-41709 8.8 VMware ESXi 8.0 / 9.0, VMware Cloud Foundation (per a single source) Unconfirmed — claimed KEV addition on 2 Nov from a single low-authority source only (logging-evasion / hostd desynchronisation; alleged Warp Panda / UNC5221 use). Verify against CISA KEV before acting If true, hiding hypervisor logs and reading guest disks would threaten virtualised core and payment systems. Critique: one low-authority source is not enough. Do not treat this as confirmed
CVE-2026-64618 9.8 (secondary source; the Apache advisory itself gives no CVSS and rates severity “important”) Apache Fineract through 1.15.0 (fixed in 1.16.1) — advanced search API /fineract-provider/api/v1/search/advance, outStandingAmountPercentageCondition Not exploited / no PoC — per the SecurityOnline 2 Nov roundup Direct: Fineract is a core and digital-banking platform. SQL injection in loan search could expose or change financial records, if the system is exposed to the internet or to a wide internal network. Critique: the 9.8 score comes from a secondary source. Apache itself gives no score and calls the flaw “important”. Serious does not yet mean exploited — no use was recorded
CVE-2026-65874 8.8 Apache Fineract ≤1.15.0 (fixed in 1.16.1) — Center / datatable endpoints, ORDER BY SQLi (authenticated read access, regex bypass) Not exploited / no PoC — per the same roundup Direct, same as above
CVE-2026-89774 8.8 Android kernel Bluetooth (SCO) — Android 14–17 Not exploited — November bulletin; no exploitation flagged, no confirmed PoC Mobile-banking fleet: Bluetooth kernel flaw on staff/customer devices; patch via the 2026-11-05 patch level
CVE-2026-55275 / 55283 / 58984 8.4 each Android System (55275: Android 16+; remote/local privilege escalation) Not exploited — November bulletin Mobile-banking / BYOD privilege-escalation risk; no targeted exploitation flagged
CVE-2026-58885 8.4 Android (confused-deputy permission bypass, local privilege escalation, no user interaction) Not exploited, not in KEV Same mobile-fleet relevance
CVE-2026-58882 (“SMS of Death”) Not scored in sources found Android telephony framework, Android 12+ (Pixel / Galaxy reported); WAP Push background processing PoC published 29 Oct (pre-window); patch in Oct/Nov updates for Android 14+; older unpatched devices remain exposed Mobile availability risk for banking customers and staff: signal loss or a bootloop after about 20 rapid messages. On the evidence found, this is not a credential-theft route. Do not present it as one
CVE-2026-103310 5.3 PayHere Payment Gateway WordPress plugin 2.4.0–2.4.5 (merchant secret unset by default) Not assessed — published 2 Nov; unauthenticated forged payment notifications can mark orders paid without payment Payments: relevant only where this plugin fronts a merchant checkout; not a core SWIFT / bank-gateway flaw

Showing all 14 watchlist rows.

Bulletin totals, for triage: the Android November bulletin has 216 fixes, 23 of them critical (65 Framework, 53 System, 30 MediaTek). They sit across patch levels 2026-11-01 (119 fixes) and 2026-11-05 (97 kernel and chipset fixes). The 2026-11-05 level covers the bulletin. Critique: a fix count is not a risk ranking. Most of these flaws have no reported use. The Apache 2 Nov roundup also covers Syncope identity flaws (including CVE-2026-113687, a sandbox escape, reported 2 Nov 22:05) and Arrow Rust CVE-2026-111959. The Syncope scores could not be verified from the snippet, so they are not shown as single rows.

Supply chain & third-party risk

The problem is often at the vendor, not the bank. A service coming back is not the same as an answer on cause or exposure.

Abrigo / Sageworks — restored, unconfirmed

Sageworks was taken offline on 30 Oct after “irregular activity”. It was partly restored on 2 Nov (reported 2 Nov 14:00 ET by BleepingComputer). More than 2,400 US banks and credit unions were affected. Borrower-facing features were still down. Critique: Abrigo called this “irregular activity”, not a breach. That wording leaves the main question open: was data taken, or not? There is no breach confirmation for the outage. No link has been shown to the earlier ShinyHunters claim of 1.7m Salesforce records taken from Abrigo. Researchers advise rotating Sageworks API keys as a precaution.

AU Small Finance Bank — claim still unverified

The bank said on 2 Nov that it is investigating a possible leak on a Salesforce-hosted SaaS platform. It says core systems are unaffected and services are normal. Salesforce said it found no flaw at its end. Critique: “core systems are unaffected” does not rule out a leak from the hosted platform. The ScarlettGroup claim — KYC, PAN/Aadhaar, bank statements, CIBIL reports, loan agreements — remains unconfirmed. So do the customer count and whether the Salesforce platform is the source.

CTOS — services restored

CTOS restored credit-reporting services after a cybersecurity breach. This was reported on 2 Nov (BursaKL). Critique: the report gives no detail on what was exposed. Restoration alone does not answer that question.

Spandana Sphoorty — status update only

Business Standard (2 Nov 13:31 IST) adds detail. The ~₹7.8 crore in unauthorised transfers on 1 Nov went to 82 beneficiary accounts. Services were stopped. A complaint was lodged on 1 Nov. A cyber-fraud insurance claim is being filed. Critique: a claim being filed is not a claim accepted or paid. It should not be read as “no loss”. No recovery, reversal, or freeze was confirmed in this window. This item was in the Monday briefing. It is not new.

Emerging fraud & attack vectors

Fake Binance “$150 compensation” scams

Fake “$150 compensation” screenshots are circulating. So are “check your reward hub” and claim links. They use the Binance incident as a lure. Binance states no cash-voucher campaign is running. Proposed community rewards were still waiting for regulatory approval at 1 Nov. Critique: the scam's claim is false on Binance's own statement. Warn customers through official channels only. Do not repeat the claim links.

Mule-account laundering — Assam, India

Six arrests were made on 28–30 Oct and reported on 2 Nov. The network operated across states for about 2 years. It included an SBI account. Money was credited, then withdrawn quickly, over 47 days (22 Jun – 5 Aug 2026). “Several crores” were allegedly siphoned. Critique: these are police claims at arrest stage. The suspected Pakistan-intelligence link is under probe only.

DDoS — multi-day attacks are the planning case

Qrator reporting (2 Nov) describes a Cyprus bank hit by a 200-hour DDoS attack in Q3 2026. Fintech accounted for 31.3% of Q3 DDoS. Critique: these are one vendor's figures for one quarter. They are a reason to plan for multi-day attacks, not a measure of any one bank's risk. The practical point stands: test multi-day DDoS plans and keep DORA-aligned resilience evidence. Do not plan for a single day only.

CyberDakait mobile trojans — context, not new

A 3 Nov Netcrook republication is recirculating an older Group-IB report, dated 28 Oct. It lists 7 families (GhostBat/GhostGrab, cyb3rx, appkjl, godz, d-passive, d-shine, tenxen), 17,960 devices, 7,611,443 SMS intercepted, 11 Indian banks and 2 government programmes impersonated, APKs via phishing and GitHub, and Firebase/Telegram C2. Critique: republication is not new activity. This is not a new 24-hour item. It is included only because it is recirculating.

Indicators & defensive actions

Only indicators the sources actually published are listed. Where no technical indicators were published, that gap is stated. It is not filled in.

Notable IOCs & behavioural indicators

  • Binance / TraderTraitor (FBI, 31 Oct, republished 2 Nov): 628 wallet addresses to block — 608 Ethereum, 19 Bitcoin, 1 Solana. Stolen funds were converted mostly to ETH. Onward laundering via DeFi and instant-swap services is expected. Screen deposits, withdrawals and any counterparty that touches these addresses. Note: a freeze is not a return of funds.
  • Mercado Bitcoin: no wallet addresses, hashes, or domains were published in the Chainalysis blog excerpt found. The only indicator is behaviour: a multi-chain drain “in waves”, largest in BTC/ETH, then Base/Tron/Polygon. Critique: without addresses, there is nothing to block from this source. The useful window is the first hours, when stablecoin issuers can still freeze funds. Prioritise issuer and law-enforcement escalation over address lists that were not published.
  • Ivanti chain: hunt for wu.cgi uploads in /home/runtime/tmp/ under MD5-named files, Perl execution racing deletion, dsinvoked config-trust abuse, AD queries for LAPS passwords and BitLocker recovery keys, and any Connect Secure appliance still on ≤25.1.1.2 / ≤22.8R2.5 (or 25.1.2.2 per VECTR-CAST). A clean Integrity Checker result does not clear an appliance.
  • Akira / Pear / Settra: no hashes, IPs, or domains were in the leak-tracker sources found. The only indicators are the leak claims themselves (130 GB pending for Princeton; wire amounts and trial-balance totals for Kingdom Title). Use them to scope exposure — were those records in the claimed set? Do not treat them as technical indicators.
  • Fraud: fake Binance “$150 compensation” screenshots and “check your reward hub” / claim links. Assam mule pattern: money is credited, then withdrawn quickly, in the same account, over weeks.
  • Sageworks / Salesforce third-party: no indicators were published. The only signal is behaviour: a vendor “irregular activity” shutdown (30 Oct), a partial restoration (2 Nov), and no breach confirmation. Use vendor status pages and API-key rotation as the control. Do not wait for a vendor indicator feed that does not exist here.

Prioritised actions — SOC

  1. Block or screen the FBI's 628 TraderTraitor addresses. Alert on any ETH-conversion or DeFi-swap pattern that touches Binance- or Mercado-related flows. Warn customers about the fake-$150 scam through official channels only. Do not repeat the claim links.
  2. Hunt the Ivanti and Siemens estates today. Confirm every Connect Secure node is on 25.1.1.3 / 22.8R2.6. Also complete forensic triage for CVE-2026-111357. The deadline has passed, and patching alone does not close the question. Confirm Siemens Software Center ≥ V4.0.9.8 (due today). Check ClickFix and DLL-sideloading detections.
  3. Treat Abrigo/Sageworks and Salesforce-hosted loan platforms as exposed until the vendor proves otherwise. Rotate Sageworks API keys. Review vendor-access logs and the data shared with the platform. Ask Abrigo and Salesforce for written scope: which fields, which customers, and whether data was taken — yes or no. Do not close the item on “services restored”.
  4. Raise helpdesk and identity controls. This is the Scattered-Spider-style pattern. No new incident is needed to justify it. Check self-service password resets for executives, Azure Global Admin grants, Veeam service-account resets, and lookalike domains that imitate the bank.
  5. Test DDoS readiness for more than one day. The Cyprus bank faced a 200-hour attack in Q3. Fintech took 31.3% of Q3 DDoS (Qrator). Keep tested, multi-day plans and DORA-aligned resilience evidence.

Prioritised actions — Vulnerability Management

  1. Today: Ivanti 25.1.1.3 / 22.8R2.6, plus forensic triage. Siemens ≥ V4.0.9.8. GitLab to 19.2.8 / 19.3.5 / 19.4.2. Also check custom container images. They can drop required patches, as in the Alpine Linux case.
  2. This week: Cisco ASA/FTD for CVE-2026-76418 (DoS only, per reporting — do not treat it as RCE). Apache Fineract to 1.16.1 (both SQLi CVEs) and Syncope upgrades. Android fleet to the 2026-11-05 patch level (or the latest OEM build, plus Play system updates for Media and Codecs).
  3. Verify before emergency change: VMware CVE-2026-41709. Check CISA KEV and Broadcom VMSA-2026-0006.1 first. Do not cite the single-source claim as fact.
  4. Watch. Do not yet close: Binance's full ZK proof-of-reserves (due 3 Nov UTC). Re-check after the UTC day ends. Check that it covers balances after the 1 Nov withdrawals, not only the 31 Oct snapshot. Also watch: Abrigo's root-cause statement, the AU SFB investigation scope, and Mercado Bitcoin's reopening and final loss figure (Chainalysis ~$49m vs the exchange's ~$38m — still unreconciled).

Could not verify

  • No new FIN7/Carbanak, LockBit, RansomHub, Cl0p, or bank-IAB reporting dated 2–3 Nov was found. Absence in search is not proof of inactivity.
  • No wallet addresses, hashes, or domains for Mercado Bitcoin, Akira/Princeton, Pear/Neiman, or Settra/Kingdom Title were published in the sources found. Without them, those items cannot be blocked or hunted as technical indicators.
  • No victim confirmation was found for Princeton Management, Neiman & Company, or Kingdom Title (beyond leak posts). None was found for AU Small Finance Bank (beyond its investigation statement) or Abrigo (beyond “irregular activity”).
  • Binance's full ZK proof-of-reserves was not confirmed as published by the 10:45 SGT cutoff. No Siemens completion proof was found. No Ivanti post-deadline compliance statement was found. In each case, “not found” means not found in this window. It does not mean it does not exist.
  • Score conflicts are left open, not resolved: Ivanti CVE-2026-111357 (8.8 vs 7.0), Siemens CVE-2026-110936 (8.4 in v4 vs 6.7 in v3.1), Fineract CVE-2026-64618 (9.8 from a secondary source vs Apache “important”, with no CVSS).
  • Single-source claims from low-authority sites — notably VMware CVE-2026-41709 — are marked unconfirmed. They are not adopted as fact.

Sources

← Back to main page