Last updated: November 2, 2026 at 1:20 PM UTC
All 957 Vulnerability 399 Breach 144 Threat 407 Defense 7

Compromised ConnectWise Cloud Backup credential lets attackers sign in to 173 Microsoft 365 tenants

Huntress observed attackers abusing a compromised Microsoft 365 OAuth credential for ConnectWise Cloud Backup, formerly SkyKick, to sign in to 173 partner and customer tenants. The credential works against every tenant the app is consented in, letting attackers obtain Microsoft Graph tokens and reach mailboxes, files, and directory data. In at least one tenant, a ConnectWise app added itself to the Global Administrator role and created new client secrets. Token acquisition came from a single IP on October 15, moving through tenants in sorted order. ConnectWise closed Cloud Backup access until all credentials are reset, and issued tokens stay valid for up to 90 minutes.

Check
If you use ConnectWise Cloud Backup, keep the application disabled until credentials are reset, enable Microsoft Graph activity logs, and audit for credentials added since October 13.
Affected
Microsoft 365 tenants that consented to the ConnectWise Cloud Backup app could be accessed with a compromised credential, exposing mailboxes, files, and directory data to attackers.
Fix
Disable the affected ConnectWise applications, review service principal sign-ins for application ID 506e08f9 and IP 144.172.64.128, revoke added secrets, and check for apps granting themselves admin roles.

Typosquatted Arch Linux AUR package imitating yay runs attacker code as root at install time

A malicious Arch User Repository account uploaded typosquatted packages, including yyay, which imitates the popular yay helper, with an install scriptlet that runs arbitrary downloaded code as root at pacman install or upgrade time. The payload was pulled from a personal project on a Russian code-hosting site, and the attacker left the normal install functions empty while placing the malicious command outside them. A malware scanner flagged yyay with high confidence, and a maintainer confirmed the payloads, banned the account, and deleted its packages. The incident follows an earlier AUR malware wave in July that briefly halted uploads across the repository.

Check
Verify AUR package names carefully before installing, review PKGBUILD and install scriptlets for commands that fetch and run remote code, and avoid lookalikes of yay and paru.
Affected
Arch users who installed the typosquatted AUR package ran attacker-controlled code as root at install time, risking credential theft, backdoors, or rootkits.
Fix
Remove any suspicious AUR packages, inspect systems that installed them for root-level compromise, rebuild from a clean state if needed, and install only vetted AUR helpers.

Low-cost MediaTek Android phones ship with system-level malware turning them into residential proxy nodes

Bitdefender detailed Midnight Mimosa, a campaign in which low-cost Android phones built on MediaTek platforms ship with a preinstalled system component, com.android.system.lite, that runs with system privileges. It grants itself accessibility, notification, and SMS permissions, installs and removes apps silently, performs ad fraud through an invisible overlay, and turns devices into residential proxy relays and botnet nodes. It disables the Play Store while dropping payloads to evade Play Protect. Bitdefender also found 13 related Play Store apps, and most infections are in Mexico, France, and Italy. Because the component sits in the system partition, users cannot remove it without firmware-level intervention.

Check
Avoid low-cost MediaTek Android devices from untrusted brands for sensitive use, and treat preinstalled system apps like com.android.system.lite as uncleanable without firmware reflashing.
Affected
Affected phones carry a system-partition component that silently installs apps, commits ad fraud, and relays residential-proxy and botnet traffic, and it cannot be removed by uninstalling.
Fix
Source Android devices through trusted vendors, reflash or replace compromised firmware, monitor networks for residential-proxy traffic, and remove the 13 related Play Store apps Bitdefender identified.

Ledger confirms hardware implant in wallets sold through reseller CryptoBilis after cryptocurrency theft reports

Ledger confirmed that a hardware wallet sold through the reseller CryptoBilis contained an unauthorized hardware implant, following reports of stolen funds from buyers in Southeast Asia. A pseudonymous blockchain investigator put losses above 86 million dollars, while Ledger described a limited number of affected devices, all sold through that reseller. Ledger paused sales through CryptoBilis, which halted all hardware wallet sales pending the investigation. Ledger advised buyers from the past 90 days not to set up unconfigured devices, and to move assets to a new signer with a fresh seed if a device was already initialized. Users should avoid unauthorized resellers.

Check
If you bought a Ledger from CryptoBilis in the last 90 days, do not initialize unconfigured devices and move any existing assets to a new signer with a fresh seed.
Affected
Ledger hardware wallets bought through the reseller CryptoBilis may contain an implant that has been linked to cryptocurrency theft from buyers in Southeast Asia.
Fix
Buy hardware wallets only from authorized channels, never reuse a pre-printed recovery phrase, move funds to a new device and seed if compromise is possible, and never share recovery phrases.

Attackers hijack Danfoss refrigeration controllers to spoil stock across hundreds of French supermarket stores

Attackers hijacked refrigeration controllers running older Danfoss control software at several French supermarket chains, including Intermarche, Carrefour Market, Monoprix, and Leclerc, abusing a built-in defrost feature to raise temperatures and spoil stock. French outlets reported 250 to 350 affected stores, significant financial losses, and food waste, and the Paris prosecutor opened an investigation. Researchers linked two flaws in the Danfoss AK-SM 8xxA platform, CVE-2025-41450 for authentication bypass and CVE-2025-41451 for command injection, though how the controllers were reached is unconfirmed. One researcher found 2,752 Danfoss systems exposed online, 1,590 of them in France.

Check
Inventory internet-exposed Danfoss AK-SM 8xxA refrigeration controllers, remove them from direct internet access, update to current firmware, and review for unauthorized configuration changes.
Affected
Internet-exposed Danfoss refrigeration controllers on older software can be hijacked to manipulate defrost and temperature settings, spoiling stored goods, as seen across hundreds of French stores.
Fix
Place refrigeration controllers behind VPN or network segmentation, patch Danfoss AK-SM platforms, enforce strong authentication, and monitor for unexpected setpoint or defrost changes.

Credential-stealing GitHub Actions workflows planted across tens of thousands of repositories via compromised maintainer accounts

Socket, StepSecurity, and GitGuardian reported a resurgence of the GhostAction supply chain campaign, in which more than 500 GitHub accounts committed a credential-stealing workflow to tens of thousands of repositories since October 7. The attacker likely used maintainer personal access tokens leaked in infostealer logs, starting with the author of the pyxel game engine and spreading to other accounts. The injected workflow, disguised as a security audit, scans the working tree and full git history against 13 secret patterns, including AWS, Anthropic, OpenAI, and GitLab keys, and exfiltrates them over plain HTTP to a hardcoded address. Earlier GhostAction activity hit 772 repositories and thousands of secrets.

Check
Search repositories and forks for security-audit.yml or github_actions_security.yml workflows added since August 31, and if present assume compromise and rotate every exposed secret.
Affected
Repositories whose maintainer tokens were leaked had a rogue workflow injected that steals GitHub Actions secrets and any credentials in the working tree and git history.
Fix
Revoke compromised GitHub credentials, delete the malicious workflow from all branches and forks, rotate all exposed secrets, and store tokens outside infostealer-reachable locations.

P7 DarkSword iOS exploit kit adds keychain and crypto wallet theft with two-way command channel

iVerify detailed P7 DarkSword, a new variant of the commercial DarkSword iOS exploit kit that has circulated among financially motivated and other actors since late 2025. It reduces its on-device footprint and adds on-device keychain and cryptocurrency wallet theft plus two-way command-and-control, running inside SpringBoard and polling for commands every 15 seconds. Collected data includes iCloud Keychain, Apple Notes, Photos, and wallet contents, with commands for disk, wallet, and photo scanning and file transfer. The chain exploits WebKit and Core Audio flaws, CVE-2025-24201 and CVE-2025-31200, patched in earlier iOS releases, and is distributed through fake websites, poisoned analytics domains, and bogus crypto platforms.

Check
Keep iOS devices updated to the latest release, and for high-risk users enable Lockdown Mode and watch for the distribution lures iVerify describes.
Affected
iPhones on older iOS versions reachable by the DarkSword chain can have keychain, Notes, Photos, and cryptocurrency wallet data stolen and receive remote attacker commands.
Fix
Update iOS promptly, enable Lockdown Mode for targeted individuals, avoid untrusted links and crypto sites, and monitor for the malicious domains and analytics tags iVerify and Report URI list.

Compromised Tensorlake npm package spreads Shai-Hulud worm that steals developer credentials and republishes itself

Socket and StepSecurity reported that version 0.5.144 of the tensorlake npm package, a TypeScript SDK, was published with obfuscated malware tied to the Shai-Hulud supply chain attack. A preinstall hook launches a loader that runs a worm under the Bun runtime. It harvests npm, GitHub, AWS, Vault, Kubernetes, and SSH credentials, .env files, cryptocurrency wallets, and configuration for Claude, Cursor, and other tools, then enumerates the victim's other packages and republishes them with forged provenance to spread. A PowerShell monitor watches the stolen GitHub token and runs a destructive handler if the victim revokes it, so remove the package before rotating that token.

Check
Check whether any project installed tensorlake 0.5.144, remove it before revoking tokens to avoid the destructive handler, then rotate all exposed credentials and audit republished packages.
Affected
Developers who installed the compromised tensorlake version had npm, GitHub, cloud, and SSH credentials stolen, and the worm may have republished their own packages with forged provenance.
Fix
Remove the malicious package, rotate npm, GitHub, cloud, and SSH credentials, review published packages and GitHub Actions workflows for tampering, and follow Socket and StepSecurity guidance on token revocation order.

Attackers hijack .gh, .sl, and .as registries to obtain fraudulent TLS certificates for Google domains

Google disclosed that attackers hijacked the .gh, .sl, and .as country-code registries and changed authoritative DNS records to pass domain-validation checks, obtaining at least twelve TLS certificates for seven Google-owned names including google.com.gh, google.sl, and google.as. Let's Encrypt issued eleven and ZeroSSL one, all logged between September 22 and 27 and since revoked, and Chrome also blocked them through CRLSets. Such certificates let an attacker impersonate the real sites, though Google has not confirmed any misuse and says its own systems were not breached. Google advises domain owners to monitor certificate transparency logs and publish strict CAA records tied to their certificate authority.

Check
Monitor certificate transparency logs for all owned domains, including parked and country-code names, and publish strict CAA records that name only your certificate authority.
Affected
Organizations with domains under the hijacked .gh, .sl, and .as registries could have had domain-validated certificates issued to attackers able to impersonate their sites.
Fix
Watch certificate transparency logs, publish strict CAA records tied to your certificate authority account, and report any unrequested certificates to the issuing authority through a certificate problem report.

FBI warns FortiBleed credential campaign stays active and locks administrators out of Fortinet VPN gateways

The FBI and Secret Service warned that FortiBleed, a credential-harvesting campaign against internet-facing FortiGate firewalls and SSL VPN gateways, remains active. The Russian-speaking operation uses credential stuffing and password spraying, then deploys a Go tool called FortigateSniffer to intercept authentication traffic, exploiting reused or leaked credentials and legacy SHA-256 password storage rather than a software flaw. It had collected more than 86,644 working device credentials across 194 countries as of June. Attackers create new admin accounts and reuse session cookies for persistence, and some victims are locked out when original accounts are changed or deleted. Operator overlaps link it to INC and Lynx ransomware.

Check
Review internet-facing Fortinet firewalls for unfamiliar admin accounts, reset VPN and admin passwords, terminate active sessions, and enable phishing-resistant authentication per the FBI and CISA guidance.
Affected
Internet-facing FortiGate firewalls with reused, leaked, or weakly stored credentials let attackers validate logins, add admin accounts, hijack sessions, and lock out legitimate administrators.
Fix
Reset VPN and admin credentials, remove rogue accounts such as fortiAdmin or forticloud-sync, store credentials with PBKDF2, enable strong authentication, and report incidents to the FBI and Secret Service.