Bell Canada breach: 'agentic' threat actor stole enterprise customer data from a circuit-provisioning Maximo pre-production system
SockAnalyst · Security+ certified analyst.
What happened
Bell Canada confirmed that an 'agentic' threat actor (Bell's word, suggesting AI-driven tooling) accessed some of its systems on November 17, 2026 and exfiltrated enterprise customer data. According to the breach notification Bell's Information Security Team sent to enterprise customers (seen by BleepingComputer), the attacker reached a pre-production environment of Bell's Maximo system, which Bell uses to order and provision telecommunications circuits. Possibly stolen: business contact details (names, job titles, corporate email addresses, phone numbers, business addresses), information in ticket titles, some IP addresses of network elements or systems, and limited contextual information. Bell says the dataset did not contain credentials, highly sensitive personal information, PDFs, file attachments or other supplementary Maximo data. Bell says it contained the incident immediately, customer services were not affected, it is contacting affected customers directly, and it has shared indicators of compromise and threat-hunting information with enterprise customers and the Canadian Centre for Cyber Security (CCCS) and contacted the RCMP. It has not released the IOCs publicly, has not said how the attacker got in or how many customers are affected, and says it does not know who is responsible; no one has claimed the attack.
Who's affected
Bell enterprise (business) customers whose circuit orders or tickets were in the Maximo pre-production environment. Expect targeted phishing and vishing that impersonates Bell using real contact names, ticket subjects and circuit details, and reconnaissance against the network-element IP addresses that appeared in tickets. Bell consumer accounts and services are not reported as affected.
✅ Fix / patch
- If you are a Bell enterprise customer, read Bell's notification and ask your Bell account team for the IOCs and threat-hunting information Bell says it is sharing with enterprise customers; load them into your SIEM and block lists.
- Warn staff who deal with Bell (network, procurement, finance, help desk) that attackers may know their names, roles and open tickets. Verify any unexpected Bell request, especially circuit changes, payment or banking changes, or remote-access requests, by calling a known Bell number, never one supplied in the message (Bell itself urged caution about impersonation).
- Review the network-element IP addresses tied to Bell circuits: confirm their management interfaces are not reachable from the internet, tighten ACLs, and watch them for new scanning or login attempts since November 17.
- Bell says no credentials were in the dataset, but rotate any shared secrets, portal passwords or PINs your team has ever pasted into Bell ticket text as a precaution.
🔎 Quick hunt check
Bell has published no public IOCs; enterprise customers should request them from Bell. These hunts check exposure, not this attacker's signature: (1) inbound email mentioning Bell, circuits, tickets or provisioning that does not come from Bell's real domains; (2) inbound connection attempts or authentication failures against the network-element IPs listed in your Bell circuit records since November 17, 2026; (3) help-desk or finance requests referencing Bell ticket numbers that cannot be matched to a real ticket.
MITRE ATT&CK: T1213, T1589.002, T1598
IOCs
No IOCs (IPs, domains or hashes) published by the sources yet.
No public IOCs. Bell shared indicators only with enterprise customers and the CCCS and declined BleepingComputer's request to publish them. The initial access method and attacker are unknown. T1589.002 and T1598 reflect the expected follow-on phishing/vishing risk from the stolen contact data, not observed activity. The IPs in the queries are documentation placeholders to replace with your own.
Hunt queries
Starting points built only from published indicators. Field names vary; tune before use.
```Bell Canada Maximo breach: Bell lookalike notices, probing of network-element IPs from Bell circuit records since Nov 17```
index=* earliest=11/17/2026:00:00:00
(sourcetype=*mail* OR sourcetype=*o365* OR tag=email OR tag=network OR tag=authentication)
| eval bell_circuit_ips="203.0.113.10,203.0.113.11" ``` replace with the network-element IPs that appear in your Bell circuit tickets ```
| eval sender=lower(coalesce(src_user, sender, from, SenderAddress, "")), subj=coalesce(subject, Subject, ""), dst_x=coalesce(dest_ip, dest, ""), src_x=coalesce(src_ip, src, "")
| eval signal=case(
match(subj,"(?i)\bbell\b.*(circuit|ticket|provision|order|invoice|account)|(circuit|ticket|provision).*\bbell\b") AND NOT match(sender,"@([a-z0-9-]+\.)*(bell\.ca|bell\.net|bellmts\.ca)$"), "bell_lookalike_notice",
like(",".bell_circuit_ips.",", "%,".dst_x.",%") AND (action IN ("blocked","denied","failure") OR dest_port IN (22,23,161,443,830,8443)), "probe_or_login_on_bell_circuit_ip",
true(), null())
| where isnotnull(signal)
| stats count min(_time) as first_seen max(_time) as last_seen values(subj) as subjects values(src_x) as sources values(dest_port) as ports by signal, sender, dst_x
| convert ctime(first_seen) ctime(last_seen)
| sort - count
``` Load the IOCs Bell shares with enterprise customers into a lookup and add them here ```// Bell Canada Maximo breach: Bell lookalike notices + probing of network-element IPs from your Bell circuit records since Nov 17
let Since = datetime(2026-11-17);
let BellCircuitIPs = dynamic(["203.0.113.10","203.0.113.11"]); // replace with network-element IPs from your Bell circuit tickets
let BellDomains = dynamic(["bell.ca","bell.net","bellmts.ca"]);
union isfuzzy=true
(EmailEvents | where TimeGenerated >= Since and EmailDirection == "Inbound"
| where Subject matches regex @"(?i)\bbell\b" and Subject has_any ("circuit","ticket","provision","order","invoice","account")
| where not(SenderFromDomain in~ (BellDomains)) and not(SenderFromDomain endswith ".bell.ca")
| summarize Hits = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated), Evidence = make_set(Subject, 20) by Who = SenderFromDomain
| extend Signal = "bell_lookalike_notice"),
(CommonSecurityLog | where TimeGenerated >= Since
| where DestinationIP in (BellCircuitIPs)
| where DeviceAction in~ ("deny","denied","drop","blocked","reject") or DestinationPort in (22, 23, 161, 443, 830, 8443)
| summarize Hits = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated), Evidence = make_set(strcat(DestinationIP, ":", tostring(DestinationPort), " ", DeviceAction), 20) by Who = SourceIP
| extend Signal = "probe_or_login_on_bell_circuit_ip")
| order by Hits desc⏱ CISA deadline
Not in CISA KEV as of Nov 22, 2026.
Sources
- BleepingComputer: Bell Canada says 'agentic' hacker stole enterprise customer data (Nov 20, 2026; quotes Bell's customer notification and statement)
- CBC News: Bell says it's investigating cyberattack that led to potential theft of business customer data (Nov 20, 2026)
Primary source note: Bell has not published a public statement, notice or advisory. Facts come from Bell's enterprise-customer breach notification as reported by BleepingComputer and from Bell spokesperson statements to BleepingComputer and CBC News. Bell shared its IOCs privately with enterprise customers and the Canadian Centre for Cyber Security, not publicly.
Related playbooks
- NTT Docomo: up to ~300k customer records leaked from My docomo / Online Shop · Breach · 2026-11-06
- FBI NCIC breach: the national crime database was reportedly hacked. What we know, what we don't, and the FBI's second breach in two months · Breach · 2026-11-22
- Microsoft Entra Connect Health API flaw exploited: admin email addresses and tenant metadata exposed, Microsoft notifying affected tenants · Breach · 2026-11-22
Get the SockAnalyst Weekly Brief free, every Thursday.
One email a week with the KEV deadlines, patches and hunt queries that matter. New playbooks still post here on the site every morning.
Subscribe free
SockAnalyst