On October 14, 2026, attackers began pulling access tokens from hundreds of Microsoft 365 business accounts — not by hacking the accounts directly, but by compromising ConnectWise Cloud Backup, the backup service those businesses trusted to protect their files. Within three days, 173 tenants had been accessed. ConnectWise disabled its application credentials on October 17, shutting down its own Cloud Backup service in the process.
That same week, organizations received a disclosure that contained a phrase that should concern anyone who stores personal files in the cloud: “there is no indication that backup archives were accessed,” followed immediately by “we cannot determine whether individual live tenants experienced unauthorized activity.”
In other words: we don’t think your data was taken, but we can’t be certain.
This is not a story about a corporation’s backup infrastructure. It is a story about how backup providers work, why they represent a distinct security risk, and what it means when the thing protecting your files becomes the thing that exposes them.
How the Attack Worked
ConnectWise Cloud Backup, formerly known as SkyKick, is a managed backup service. Businesses connect it to their Microsoft 365 accounts, and the service automatically backs up emails, documents, and files. To do this, it needs persistent, privileged access to those accounts — which it maintains through application credentials stored on its own infrastructure.
Attackers stole those application credentials.
What makes this attack notable is what it bypassed. When a person signs in to Microsoft 365, the account may be protected by multi-factor authentication — a prompt to your phone before access is granted. Application-level authentication does not go through this flow. The backup service authenticates as a trusted application, not as a user. There is no prompt to anyone’s phone. MFA, as most people understand it, never gets a chance to work.
Once inside via those stolen credentials, attackers were able to access customer Microsoft 365 tenants — their emails, their files, their stored documents. In some tenants, the attackers also used the compromised application access to assign themselves elevated administrative roles, including, in at least one case, Global Administrator.
The investigation found signs of unauthorized sign-ins across 173 separate Microsoft 365 environments.
The Visibility Problem
Incidents like this expose a structural issue with cloud backup: the backup provider occupies a position of deep, ongoing trust in your file ecosystem. It is not a one-time authorization. It is a standing, privileged connection that persists for as long as you use the service.
That standing connection becomes an attack surface.
Every cloud service you authorize to access your files creates another pathway through which your files can be reached. A compromised photo-printing service can access your photo library. A compromised backup service can access everything you have backed up. The more trusted services you connect, the more entry points exist.
This is different from a breach of the cloud storage provider itself. When people think about cloud security, they often think about Google or Microsoft being hacked. The reality is that the risk is often at the layer of third-party services that have been granted access — services that may have significantly less security investment than the primary providers.
What “No Evidence of Access” Actually Means
ConnectWise’s disclosure included language that is becoming a recurring feature of cloud breach notifications: an assertion that backup archives were not accessed, qualified by an acknowledgment that individual tenant activity could not be confirmed.
This language is worth understanding precisely. An investigation of a cloud breach typically analyzes access logs — records of what was accessed, when, and by whom. When a company says there is “no indication” data was accessed, it generally means the logs do not show bulk file downloads or data exfiltration. This is meaningful.
What it does not mean is that no files were read, copied in small quantities, or accessed in ways that do not generate distinctive log signals. It also does not account for data that may have been accessed before logging became complete, or for tenants where the investigation found the activity “inconclusive.”
For individuals who store personal files in backup services, “we don’t think so, but we can’t be certain” is the honest answer after a serious incident of this kind. That uncertainty is itself a form of harm — even if no files were taken, you may not be able to know.
What This Means If You Use a Cloud Backup Service
Most personal cloud backup services work by different mechanisms than managed enterprise backup. Consumer services like iCloud Backup, Google Backup, or backup features in photo apps typically authenticate with your credentials, not with a separate application-level credential managed by a backup provider.
But the structural issue applies broadly: when you authorize a third-party service to access your cloud files, that service acquires a standing connection to your data. The security of that connection depends on the security of the third party’s infrastructure — which is not something you can inspect.
A few questions worth asking about any service with access to your personal files:
What access does this service actually need? A backup service needs read access to your files. It should not need administrative access to your account or the ability to modify permissions. Granting more access than the function requires creates unnecessary risk.
How is the access revoked if the service is compromised? When ConnectWise was compromised, it disabled its own application credentials — but the administrative changes made inside individual tenants persisted. Revoking a service’s access does not automatically undo what it did while it had access.
What is this service’s breach disclosure history? Past breaches and how they were handled are the most reliable signal of a provider’s security posture. A company that has handled incidents transparently and promptly is different from one that waited or qualified its disclosure.
Who can see your backup provider’s access? In most consumer services, you can review which apps and services have been granted access to your cloud storage from your account security settings. This is worth checking — connected services from apps you no longer use may still hold standing access.
Backup Is Not the Same as Storage
There is a useful distinction between using a service for backup and using a service for intentional, deliberate storage.
A backup service copies everything it finds. Its job is comprehensiveness — catching every document, every photo, every email, whether you think about it or not. That comprehensiveness creates a copy of your complete digital life in a location you may not actively monitor, managed by a third party with privileged access.
Intentional storage is different. You choose what goes where. You maintain an inventory of what is stored. You choose providers based on their security practices, not just their convenience.
The ConnectWise incident is a reminder that the backup layer of your digital life may be the least scrutinized part of it. The primary account — your Google account, your Apple ID, your Microsoft account — gets your attention because you use it daily. The backup service is largely invisible until something goes wrong.
What to Check Now
If you use any cloud backup service — for files, emails, or photos — a few concrete checks are worth doing:
Review connected applications. In Google, check Security → Third-party apps with account access. In Apple, check appleid.apple.com → Sign-In and Security. In Microsoft 365, check account settings for connected apps. Remove any service you no longer actively use.
Check for unusual activity. Most cloud providers maintain a sign-in history. Look for access from unfamiliar locations, services, or times.
Understand your backup provider’s security posture. Specifically: how does it authenticate to your account, what level of access does it hold, and what is its disclosed incident history?
Consider what you are actually backing up. Not everything needs to be in a comprehensive cloud backup. Sensitive documents, personal photos, and financial records stored intentionally in a purpose-specific service you actively manage are under different conditions than files swept into a backup you do not monitor.
The Honest Assessment
The ConnectWise incident is unlikely to be the last supply chain attack on cloud backup infrastructure. The attack pattern — compromise a trusted intermediary to reach the accounts it serves — is well-established and applies to any third-party service with standing access to your data.
The response is not to avoid cloud storage entirely. It is to be deliberate about what has access to what, to minimize standing third-party connections where possible, and to understand that “secure backup” is a more complicated guarantee than the term implies.
Your backup provider’s security posture matters as much as your primary cloud provider’s. If you have not thought about it, now is a good time to start.
daftei does not act as an intermediary for other services or hold application-level credentials into third-party accounts. Files you store in daftei live in daftei — protected with TLS 1.3 in transit and AES-256 encryption at rest — without connecting to other cloud services or maintaining privileged access relationships that could become the next attack surface.