Rankteo Cyber Security Incidents

Microsoft: Hackers Exploit Microsoft Teams to Breach Organizations While Posing as IT Helpdesk Staff

Rankiteo.com — Fri, 24 Apr 2026 00:00:00 +0000

UNC6692 Threat Group Exploits Microsoft Teams in Sophisticated Social Engineering Attack A newly identified cyber threat group, UNC6692, is targeting enterprises through a multi-stage attack combining social engineering and custom malware, leveraging Microsoft Teams and cloud services to evade detection. The attack begins with an email bombing campaign, flooding victims with spam to create confusion. While targets are distracted, attackers impersonate IT helpdesk staff via Microsoft Teams, using external accounts to offer a fake "local patch" as a solution. Victims are directed to a spoofed "Mailbox Repair Utility" page, where they are prompted to enter credentials intentionally rejected on the first attempt to ensure password capture before exfiltration to an attacker-controlled AWS server. Once credentials are stolen, the attack deploys a modular malware toolkit dubbed the SNOW ecosystem, including: - SNOWBELT: A malicious Chromium extension for persistent access. - SNOWGLAZE: A Python-based tunneling tool for encrypted communication. - SNOWBASIN: A remote access tool enabling command execution, screenshots, and data theft. After gaining a foothold, UNC6692 moves laterally across the network using Python scripts to scan systems, targeting backup servers and dumping LSASS memory to extract password hashes. These hashes are cracked offline and used in Pass-the-Hash attacks to compromise domain controllers. Attackers then exfiltrate the Active Directory database using legitimate forensic tools like FTK Imager, delivered via Microsoft Edge, and transfer data via platforms such as LimeWire. The campaign exemplifies "living off the cloud" tactics, abusing trusted services like Microsoft Teams and AWS to bypass traditional security measures. Indicators of compromise (IoCs) include: - Phishing/payload delivery: `service-page-25144-30466-outlook.s3.us-west-2.amazonaws[.]com` - SNOWBELT C2: `cloudfront-021.s3.us-west-2.amazonaws[.]com` - SNOWGLAZE WebSocket: `wss://sad4w7h913-b4a57f9c36eb.herokuapp[.]com/ws` - Data exfiltration: `service-page-11369-28315-outlook.s3.us-west-2.amazonaws[.]com` The attack underscores the risks of external Teams communications and the need for enhanced monitoring of browser-based activity and cloud service abuse.

Ollama: Hackers Exploit Ollama Model Uploads to Leak Server Data

Rankiteo.com — Fri, 24 Apr 2026 00:00:00 +0000

Critical Unpatched Vulnerability in Ollama Exposes Sensitive Data to Attackers Cybersecurity researchers have identified a severe, unpatched vulnerability in Ollama, a widely used open-source platform for running large language models (LLMs) locally. Tracked as CVE-2026-5757, the flaw resides in Ollama’s model quantization engine and allows unauthenticated attackers to steal sensitive server data by uploading a maliciously crafted AI model file. ### How the Exploit Works Ollama’s quantization process designed to optimize model performance by reducing numerical precision contains an out-of-bounds memory vulnerability in its handling of GPT-Generated Unified Format (GGUF) files. When an attacker uploads a specially crafted GGUF file and triggers quantization, the engine reads beyond safe memory limits due to three critical flaws: 1. Unchecked file metadata – The engine trusts user-provided metadata without verifying its alignment with the actual data size. 2. Unsafe memory operations – A Go-based memory slice extends into the application’s heap, enabling unauthorized access. 3. Data exfiltration via API – Stolen memory (including sensitive data) is written to a new model layer and can be extracted through Ollama’s registry API. ### Potential Impact Since the vulnerability grants access to the server’s heap memory, attackers can silently extract highly sensitive data processed during normal operations, including: - API keys - Private user data - Proprietary intellectual property Worse, the exploit could enable full server compromise, allowing attackers to move laterally within a network, establish persistence, and evade detection by standard security tools. ### Discovery & Current Status The flaw was uncovered by security researcher Jeremy Brown, who employed AI-assisted vulnerability research techniques. As of late April 2026, the CERT Coordination Center has been unable to contact Ollama’s vendor, leaving the vulnerability unpatched. ### Mitigation Measures Until an official fix is released, organizations running Ollama are advised to: - Disable or restrict model upload functionality on exposed servers. - Limit deployments to isolated or trusted networks. - Only use AI models from verified sources. - Enforce strict network controls to block unauthorized data exfiltration. The incident underscores the growing risks of supply chain attacks in AI infrastructure, particularly in open-source tools with widespread adoption.

Telegram: Hackers Use Pastebin-Hosted PowerShell Script to Steal Telegram Sessions

Rankiteo.com — Fri, 24 Apr 2026 00:00:00 +0000

New Telegram Session-Stealing PowerShell Script Discovered on Pastebin Cybersecurity researchers at Flare have identified a malicious PowerShell script hosted on Pastebin, designed to steal Telegram session data from both desktop and web-based clients. The script, titled "Windows Telemetry Update," masquerades as a legitimate Windows system update to deceive users into executing it. Upon execution, the script first gathers host metadata including the victim’s username, computer name, and public IP address before targeting Telegram’s session files in directories like `%APPDATA%\Telegram Desktop` and `%APPDATA%\Telegram Desktop Beta`. These files are compressed into a temporary diag.zip archive and exfiltrated via the Telegram Bot API. Two versions of the script were found on Pastebin under the same account. The initial version (v1) contained a broken multipart upload implementation, preventing successful data exfiltration. The operator later released a corrected version (v2), which properly transmits the stolen data using the `sendDocument` endpoint. The debugging process, visible in the Pastebin post history, offers rare insight into the development of session-stealing tools. The script forcibly terminates the Telegram process to bypass file locks before compressing session data. If the primary exfiltration method fails, a fallback `WebClient UploadFile` ensures the archive reaches the attacker. The script then deletes diag.zip to minimize forensic traces. A separate web-based stealer component, sharing the same bot infrastructure, captures Telegram Web’s `localStorage` session keys, allowing attackers to reconstruct authenticated sessions without passwords or SMS verification. Flare’s analysis suggests the script was still in testing rather than active deployment. However, the functional v2 variant and shared infrastructure with the web-based stealer indicate the capability is now validated and could be scaled for broader use. The lack of obfuscation, persistence, or automated delivery mechanisms further supports this assessment.

Udemy, McGraw-Hill, Vercel and Harvard University: Udemy Data Breach – ShinyHunters Allegedly Claims Compromise of 1.4M User Records

Rankiteo.com — Fri, 24 Apr 2026 00:00:00 +0000

ShinyHunters Claims Major Data Breach of Udemy, Threatens to Leak 1.4M Records On April 24, 2026, the cybercriminal group ShinyHunters announced a data breach targeting Udemy, one of the world’s largest online learning platforms, alleging the theft of over 1.4 million records containing personally identifiable information (PII) and internal corporate data. The group issued a "Pay or Leak" ultimatum, demanding a response from Udemy by April 27, 2026, or risk public exposure of the stolen data. ShinyHunters, a financially motivated extortion group active since 2019, has built a reputation for high-profile breaches, including the 2020 theft of 200 million records from 13 companies. In 2026 alone, the group has intensified attacks on SaaS platforms and the education sector, with recent victims including Vercel, McGraw-Hill, and Harvard University (where 115,000 alumni records were exposed). Google Threat Intelligence tracks the group under the designation UNC6240, noting its shift from traditional network exploitation to social engineering, MFA bypass, and credential harvesting. ShinyHunters often exploits third-party integrations and compromised vendor credentials, as seen in the Vercel breach, where a third-party vendor (Context.ai) served as the entry point. The education sector remains a prime target, with ShinyHunters previously breaching India’s Unacademy, stealing over 10 million user accounts. As of publication, Udemy has not confirmed or denied the breach, and researchers continue monitoring the group’s leak site for potential data release following the deadline. The incident underscores the group’s evolving tactics and persistent focus on high-value targets.

Sri Lankan Finance Ministry: Sri Lankan government hack sees $3.7m destined for Australia stolen

Rankiteo.com — Fri, 24 Apr 2026 00:00:00 +0000

Sri Lankan Finance Ministry Hit by $3.7 Million Cyber Heist Targeting Debt Payments The Sri Lankan government has confirmed a cyber attack on its Finance Ministry, resulting in the theft of over $3.7 million the largest sum ever stolen by hackers from a Sri Lankan state institution. The funds, earmarked for debt repayments to Australia, were diverted after attackers breached the ministry’s email servers and computer systems. Australian High Commissioner to Sri Lanka, Matthew Duckworth, acknowledged the incident, stating that both governments were aware of "irregularities" in the payments. While Sri Lankan authorities have not disclosed the nature of the attack or identified the perpetrators, Finance Ministry Secretary Harshana Suriyapperuma revealed that hackers altered payment details to redirect the funds. The Criminal Investigation Department (CID) and the Financial Intelligence Unit of the Central Bank of Sri Lanka have been notified, and a formal investigation led by a committee including two deputy Treasury secretaries has been launched. The breach was discovered after officials detected unauthorized access to the ministry’s email servers. Sri Lanka, still recovering from its 2022 economic crisis and default on $46 billion in external debt, remains under scrutiny as authorities work with Australian officials to trace the stolen funds. Australia has reaffirmed its commitment to supporting Sri Lanka’s debt sustainability efforts amid the ongoing probe.

Coupang: South Korea says Coupang data breach probe affects US security talks

Rankiteo.com — Fri, 24 Apr 2026 00:00:00 +0000

South Korea’s Coupang Data Breach Complicates US Security Talks South Korea’s National Security Adviser, Wi Sung-lac, confirmed on Friday that an ongoing investigation into a major data breach at e-commerce giant Coupang is creating friction in security negotiations with the United States. The government has emphasized that the probe should proceed independently of broader security discussions, as linking the two could undermine diplomatic progress. The breach, which has drawn regulatory scrutiny, has raised concerns about its potential impact on sensitive bilateral talks. While South Korea maintains that private sector issues should not derail strategic cooperation, the incident has introduced complications in high-level consultations. Details on the scope of the breach, including the number of affected users or the nature of exposed data, remain undisclosed. The situation underscores the growing intersection of cybersecurity incidents and geopolitical relations, particularly as digital threats increasingly influence national security priorities.

Innovative Scientific Solutions and LLC: Innovative Scientific Solutions Data Breach Exposes Personal Information: Murphy Law Firm Investigates Legal Claims

Rankiteo.com — Thu, 23 Apr 2026 00:00:00 +0000

Innovative Scientific Solutions Suffers Major Data Breach, Exposing Sensitive Personal Information On April 23, 2026, Oklahoma-based Innovative Scientific Solutions, LLC disclosed a significant data breach after detecting suspicious activity on its network. A forensic investigation revealed that cybercriminals had infiltrated the company’s inadequately secured systems, gaining access to files containing sensitive personal data belonging to thousands of individuals. The exposed information includes names, Social Security numbers, driver’s license numbers, financial account details, credit/debit card information, medical treatment records, and health insurance data. The breach raises serious concerns about potential identity theft, fraud, and the sale of compromised data on the dark web. Murphy Law Firm has launched an investigation into the incident and is exploring legal action, including a potential class action lawsuit, on behalf of affected individuals. The firm specializes in data breach litigation and has previously secured favorable outcomes for clients in similar cases. No further details on the breach’s origin, the number of impacted individuals, or the timeline of the attack have been released. The incident underscores the ongoing risks posed by inadequate cybersecurity measures in safeguarding sensitive personal information.

Mozilla: Privacy Vulnerability in Firefox and TOR Browsers

Rankiteo.com — Thu, 23 Apr 2026 00:00:00 +0000

Firefox and Tor Browsers Affected by Privacy-Tracking Vulnerability Security firm Fingerprint uncovered a privacy flaw in Firefox and the Tor Browser that could allow websites to track users even in private browsing or anonymity-focused modes. The vulnerability, stemming from low entropy in how browsers retrieve non-sensitive metadata, created unique system fingerprints that persisted despite privacy protections. Mozilla addressed the issue in Firefox 150, released on April 21, 2026, after Fingerprint responsibly disclosed the flaw. The weakness exploited inconsistencies in database metadata retrieval, enabling tracking across sessions undermining the privacy assurances of private browsing and Tor’s anonymity features. The discovery highlights broader risks in browser security, particularly as AI-driven tools like Anthropic’s Claude Mythos may uncover similar vulnerabilities in the future. While the patch resolves the immediate threat, the incident underscores the ongoing challenges in maintaining robust privacy protections.

Centreon: KARE 11

Rankiteo.com — Thu, 23 Apr 2026 00:00:00 +0000

Cyberattack Targets French Government Agencies via Compromised Software Update A sophisticated cyberattack recently disrupted operations across multiple French government agencies after attackers exploited a compromised software update. The incident, detected in early June 2024, involved malicious actors infiltrating the supply chain of a widely used administrative software provider, Centreon, to distribute malware to its clients. The attack primarily affected agencies relying on Centreon’s IT monitoring tools, with initial reports indicating disruptions in data access and system functionality. French cybersecurity agency ANSSI (Agence Nationale de la Sécurité des Systèmes d’Information) confirmed the breach stemmed from a trojanized update pushed to users, allowing threat actors to gain persistent access to internal networks. While the full scope of the compromise remains under investigation, early findings suggest the attackers sought to exfiltrate sensitive administrative data rather than deploy ransomware. ANSSI has attributed the attack to a state-sponsored group, citing tactics consistent with advanced persistent threat (APT) actors. No specific nation-state has been publicly named. The incident underscores the growing risk of supply chain attacks, where trusted software vendors become unwitting vectors for cyber espionage. French authorities have since issued emergency patches and urged affected agencies to isolate compromised systems, though the long-term impact on government operations is still being assessed.

UK’s National Cyber Security Centre and Volt Typhoon: Chinese hackers are using everyday devices to hack UK firms, warns watchdog

Rankiteo.com — Thu, 23 Apr 2026 00:00:00 +0000

China-Linked Hackers Exploit Everyday Devices in Global Espionage Campaign The UK’s National Cyber Security Centre (NCSC), alongside cybersecurity agencies from nine other countries including the U.S., Australia, Canada, and Germany has issued a warning about a sophisticated cyber-espionage campaign tied to China. The threat involves the hijacking of common internet-connected devices, such as Wi-Fi routers, printers, and webcams, to create covert networks (or "botnets") for surveillance and data theft. These botnets primarily target outdated or unpatched devices, using them as launchpads for attacks while obscuring the attackers' origins. The NCSC’s CEO, Richard Horne, described China’s cyber capabilities as "eye-watering," emphasizing that Beijing’s intelligence and military agencies now operate as a "peer competitor" in cyberspace. The shift in tactics leveraging compromised consumer and small office devices marks a significant evolution in China-linked cyber operations. The advisory highlights that these covert networks are often maintained by private Chinese firms, with one example involving a company that infected 200,000 devices worldwide. A notable group, Volt Typhoon, has been linked to infiltrations of critical U.S. infrastructure, including rail, aviation, and water systems. The NCSC warns that multiple threat actors may share a single botnet, making attribution and defense more challenging. To mitigate risks, the NCSC recommends organizations map their IT systems including connections to consumer broadband networks enforce multi-factor authentication for remote access, and restrict external device connections. While the guidance is aimed at businesses, the widespread use of compromised household devices underscores the broader threat landscape. Earlier this year, Google disrupted a similar "residential proxy" network, demonstrating the global scale of these operations. The NCSC’s advisory, published on Thursday, confirms that China-backed hackers continue to refine their methods, posing a persistent and evolving risk to cybersecurity.

Asurion, npm and GitHub: Self-Propagating Supply Chain Worm Hijacks npm Packages to Steal Developer Tokens

Rankiteo.com — Wed, 22 Apr 2026 17:33:00 +0000

New Supply Chain Worm Targets npm and PyPI, Stealing Developer Credentials Cybersecurity researchers from Socket and StepSecurity have uncovered a self-propagating supply chain worm, dubbed CanisterSprawl, that exploits compromised npm packages to steal developer credentials and spread malicious updates. The campaign, active in recent weeks, leverages an ICP canister for data exfiltration a tactic previously used by TeamPCP to evade takedowns. ### Affected Packages The following npm packages were found to contain malicious postinstall hooks that trigger the worm during installation: - `@automagik/genie` (v4.260421.33–4.260421.40) - `@fairwords/loopback-connector-es` (v1.4.3–1.4.4) - `@fairwords/websocket` (v1.0.38–1.0.39) - `@openwebconcept/design-tokens` (v1.0.1–1.0.3) - `@openwebconcept/theme-owc` (v1.0.1–1.0.3) - `pgserve` (v1.1.11–1.1.14) ### Attack Mechanics Once executed, the malware harvests sensitive data from developer environments, including: - npm tokens (used to publish poisoned package versions) - SSH keys, `.git-credentials`, and `.netrc` files - Cloud credentials (AWS, Google Cloud, Azure) - Kubernetes, Docker, Terraform, and Vault configurations - Local `.env` files and shell history - Browser-stored credentials (Chromium-based browsers) - Cryptocurrency wallet extensions Stolen data is exfiltrated to: - An HTTPS webhook (`telemetry.api-monitor[.]com`) - An ICP canister (`cjn37-uyaaa-aaaac-qgnva-cai.raw.icp0[.]io`) The worm also includes PyPI propagation logic, generating malicious Python packages via Twine if credentials are present, effectively turning one compromised environment into multiple package infections. ### Additional Threats in Open-Source Ecosystems - Compromised PyPI Package: Versions 2.6.0–2.6.2 of the legitimate `xinference` package were altered to include a Base64-encoded payload, fetching a second-stage credential harvester. While the payload includes the marker "# hacked by teampcp," the group denied involvement, suggesting a copycat attack. - Fake Kubernetes Tools: Malicious npm (`kube-health-tools`) and PyPI (`kube-node-health`) packages disguised as Kubernetes utilities deploy a Go-based binary that sets up: - A SOCKS5 proxy - A reverse proxy - An SFTP server - An LLM proxy (routing requests to Chinese LLM APIs, enabling secret exfiltration and malicious payload injection). - Asurion-Themed npm Attack: Between April 1–8, 2026, threat actors published fake npm packages (`sbxapps`, `asurion-hub-web`, `soluto-home-web`, `asurion-core`) impersonating Asurion and its subsidiaries. Stolen credentials were first sent to a Slack webhook, then to an AWS API Gateway endpoint, later obfuscated with XOR encoding. - GitHub Actions Exploitation: A campaign dubbed prt-scan, active since March 11, 2026, abuses the `pull_request_target` GitHub Actions trigger to steal secrets. Attackers: - Fork repositories using the trigger - Inject malicious payloads into CI workflows - Open pull requests to trigger credential theft - Publish malicious npm packages if tokens are found While the campaign had a <10% success rate, most victims were small projects, though a few exposed cloud credentials and persistent API keys. ### Impact & Trends These incidents highlight the growing sophistication of supply chain attacks, with threat actors increasingly targeting npm, PyPI, and CI/CD pipelines to propagate malware. The use of resilient exfiltration methods (ICP canisters, obfuscated endpoints) and multi-stage credential theft underscores the need for heightened scrutiny in open-source dependency management.

Bitwarden: Bitwarden CLI npm package compromised to steal developer credentials

Rankiteo.com — Wed, 22 Apr 2026 00:00:00 +0000

Bitwarden CLI Compromised in Supply Chain Attack Targeting npm On April 22, 2026, attackers briefly compromised the Bitwarden CLI by uploading a malicious version of the `@bitwarden/cli` npm package (version 2026.4.0). The package, available between 5:57 PM and 7:30 PM ET, contained a credential-stealing payload designed to spread to other projects. Bitwarden confirmed the incident, stating the breach was limited to its npm distribution channel and did not affect end-user vault data, production systems, or the legitimate CLI codebase. The company revoked compromised access, deprecated the malicious release, and initiated remediation. ### Attack Details Security firms Socket, JFrog, and OX Security reported that threat actors likely exploited a compromised GitHub Action in Bitwarden’s CI/CD pipeline to inject malicious code. The package included a preinstall script and a custom loader (`bw_setup.js`) that checked for the Bun runtime downloading it if absent before executing an obfuscated JavaScript file (`bw1.js`). The malware targeted: - npm and GitHub authentication tokens - SSH keys - Cloud credentials (AWS, Azure, Google Cloud) Stolen data was encrypted with AES-256-GCM and exfiltrated via public GitHub repositories under victims’ accounts, marked with the string "Shai-Hulud: The Third Coming" a reference to prior npm supply chain attacks. The malware also had self-propagating capabilities, using stolen credentials to inject malicious code into other packages. ### Connections to Other Attacks The attack shares infrastructure and malware overlaps with a recent Checkmarx supply chain breach, including: - The same telemetry endpoint (`audit.checkmarx[.]cx/v1/telemetry`) - Identical obfuscation routines (`__decodeScrambled` with seed `0x3039`) - Similar credential theft and GitHub-based exfiltration tactics Both campaigns have been attributed to TeamPCP, a threat actor previously linked to attacks on Trivy and LiteLLM. Bitwarden’s investigation found no evidence of broader compromise, but developers who installed the affected version were advised to rotate exposed credentials, particularly those tied to CI/CD pipelines and cloud environments.

Microsoft: Microsoft Issues Emergency .NET 10.0.7 Update to Patch Elevation of Privilege Vulnerability

Rankiteo.com — Wed, 22 Apr 2026 00:00:00 +0000

Microsoft Releases Emergency Patch for Critical .NET Privilege Escalation Flaw (CVE-2026-40372) Microsoft has issued an out-of-band security update to address a severe elevation of privilege vulnerability in the .NET framework, tracked as CVE-2026-40372. The flaw emerged as a regression in .NET 10.0.6, introduced during a routine Patch Tuesday update, and was later identified as a critical security risk after developers reported widespread decryption failures. The vulnerability stems from a cryptographic flaw in the Microsoft.AspNetCore.DataProtection NuGet package, where the managed authenticated encryptor incorrectly processed its Hash-based Message Authentication Code (HMAC). By calculating validation tags using the wrong payload bytes and discarding the resulting hash, the flaw compromises data integrity, allowing attackers to manipulate payloads and escalate privileges without triggering authentication alerts. The issue affects .NET 10 deployments running versions 10.0.0 through 10.0.6, including applications deployed in containers using unpatched base images. Organizations relying on ASP.NET Core Data Protection for securing sensitive data are particularly at risk. To remediate, development teams must: - Install .NET 10.0.7 SDK or Runtime from Microsoft’s official portal. - Update the Microsoft.AspNetCore.DataProtection dependency to version 10.0.7 in project configurations. - Rebuild and redeploy applications using fresh container images or installation packages. Microsoft has urged teams to verify the update via `dotnet --info` and report any stability issues through the .NET release feedback repository. The out-of-band patch underscores the urgency of addressing the flaw to prevent potential privilege escalation attacks.

Expel, OpenAI, Cursor and Anima: AI Tools Are Helping Mediocre North Korean Hackers Steal Millions

Rankiteo.com — Wed, 22 Apr 2026 00:00:00 +0000

North Korean Hackers Leverage AI to Steal $12 Million in Cryptocurrency Cybersecurity firm Expel has uncovered a North Korean state-sponsored hacking campaign that exploited AI tools to orchestrate a large-scale cryptocurrency theft operation. The group, dubbed HexagonalRodent, targeted over 2,000 developers working on cryptocurrency, NFT, and Web3 projects, using AI-generated malware and phishing infrastructure to siphon an estimated $12 million in just three months. Unlike highly sophisticated cybercrime syndicates, HexagonalRodent relied on AI platforms including OpenAI, Cursor, and Anima to compensate for its lack of technical expertise. The hackers used these tools to write malware, design fake company websites, and craft phishing lures, particularly fraudulent job offers aimed at developers. Victims were tricked into downloading malware-laced coding assignments, which stole credentials and, in some cases, crypto wallet keys. Security researcher Marcus Hutchins, who identified the group, noted that the operation’s success stemmed not from advanced hacking skills but from AI’s ability to automate tasks that would otherwise require significant technical knowledge. The hackers’ reliance on AI was evident in their malware, which included unusual features like excessive English-language comments and emoji-littered code hallmarks of large language model-generated software. Despite their effectiveness, the group left critical infrastructure exposed, revealing their AI prompts and a database tracking victim wallets. While the $12 million figure represents the total value of compromised wallets, researchers could not confirm whether all funds had been drained, as some wallets may have been protected by hardware security tokens. The campaign underscores how AI is lowering the barrier to entry for cybercriminals, enabling even low-skilled actors to execute high-impact attacks.

Agoda, Booking.com and Booking Holdings: Agoda refutes claims of massive data breach

Rankiteo.com — Wed, 22 Apr 2026 00:00:00 +0000

Agoda Denies Data Breach as Cybercriminals Claim Theft of 82 Million Records Asia-based travel booking platform Agoda has refuted claims of a data breach after cybercriminals alleged the theft of 82 million user records. An Agoda spokesperson stated that internal investigations confirmed the leaked data did not originate from its systems. Researchers at Cybernews analyzed a sample of 23 records provided by the attackers, which included sensitive details such as full names, identity card numbers, phone numbers, email addresses, and hotel addresses primarily linked to Malaysian users. Notably, the sample lacked reservation dates, an unusual omission that raised questions about the data’s origin. Despite this, the researchers verified the legitimacy of the exposed information. The incident follows a recent confirmation by Agoda’s parent company, Booking Holdings, of a separate breach affecting Booking.com users. That attack exposed names, phone numbers, email addresses, and reservation details, leading to a surge in reservation hijacking scams across North America, Europe, and the UK. The timing of the two incidents has heightened concerns about cybersecurity risks in the travel industry.

Microsoft: Hackers Leverage Microsoft Teams to Breach Organizations Posing as IT Helpdesk Staff

Rankiteo.com — Wed, 22 Apr 2026 00:00:00 +0000

UNC6692 Threat Group Exploits Microsoft Teams in Sophisticated Cloud-Based Intrusion Campaign A newly uncovered threat group, UNC6692, has been executing a multistage intrusion campaign targeting enterprise networks without exploiting a single software vulnerability. Instead, the attackers leverage Microsoft Teams impersonation, custom malware, and cloud infrastructure abuse to gain deep access, as revealed by Google Threat Intelligence Group (GTIG) and Mandiant in an April 22, 2026 disclosure. ### Attack Timeline & Tactics In late December 2025, UNC6692 launched a mass email bombing campaign to overwhelm victims, creating urgency and distraction. Exploiting this chaos, the group sent phishing messages via Microsoft Teams, posing as IT helpdesk staff offering assistance. The attack abused legitimate external collaboration features in Teams, bypassing technical exploits by convincing users to override security warnings. ### Infection Chain: From Teams Chat to Full Compromise 1. Initial Contact – Victims accepted a Teams chat from an external account, believing it to be IT support. 2. Phishing Link – The attacker directed victims to a fake "Mailbox Repair and Sync Utility" hosted on an AWS S3 bucket, masquerading as a legitimate tool. 3. Multi-Phase Exploitation: - Environment Gating – A script forced victims onto Microsoft Edge for optimal exploitation. - Credential Harvesting – A fake "Health Check" prompted users to re-enter passwords, ensuring accurate capture before exfiltration. - Distraction Sequence – A fake progress bar masked real-time data theft. - Malware Staging – An AutoHotkey binary and script installed SNOWBELT, a malicious Chromium extension disguised as "MS Heartbeat". ### The SNOW Malware Ecosystem UNC6692’s modular malware suite consists of three components: - SNOWBELT (JavaScript extension) – Establishes persistence, intercepts commands, and uses DGA-based S3 URLs for C2. - SNOWGLAZE (Python WebSocket tunneler) – Routes traffic via a SOCKS proxy to a Heroku C2 server, blending malicious traffic with legitimate encrypted web traffic. - SNOWBASIN (Python HTTP server) – Executes shell commands, captures screenshots, and exfiltrates files. Persistence was maintained via Windows Startup shortcuts, scheduled tasks, and a headless Edge process loading the extension. ### Post-Exploitation & Data Theft After gaining access, UNC6692: - Scanned networks for open ports (135, 445, 3389). - Used PsExec to move laterally, dumping LSASS memory via Task Manager to extract password hashes. - Employed Pass-the-Hash to authenticate to domain controllers without plaintext passwords. - Extracted Active Directory databases (NTDS.dit), SAM, SYSTEM, and SECURITY hives using FTK Imager, exfiltrating them via LimeWire. ### Cloud Abuse & Evasion Tactics A defining feature of this campaign is its "living off the cloud" strategy, using AWS S3, Heroku, and other trusted platforms for: - Payload delivery - Credential exfiltration - Command-and-control (C2) infrastructure This approach blends malicious traffic with legitimate cloud traffic, evading domain reputation filters and IP-based blocklists. ### Indicators of Compromise (IOCs) - Phishing URL Pattern: `https://service-page-[ID]-outlook.s3.us-west-2.amazonaws.com/update.html?email=` - C2 Server: `wss://sad4w7h913-b4a57f9c36eb[.]herokuapp[.]com:443/ws` - SNOWBELT C2 URL Pattern: `https://[a-f0-9]{24}-[0-9]{6,7}-[0-9]{1}.s3.us-east-2.amazonaws[.]com` - Masquerading Files: `RegSrvc.exe` (AutoHotKey), `Protected.ahk`, `SysEvents` (SNOWBELT extension directory). The campaign underscores how employee trust in enterprise tools rather than technical vulnerabilities can be the weakest link in cybersecurity. Organizations are advised to monitor Teams external access, browser extensions, and cloud egress traffic to detect similar threats.

Notion: Notion public pages found leaking user emails and profile pictures

Rankiteo.com — Wed, 22 Apr 2026 00:00:00 +0000

Notion Privacy Leak Exposes User Metadata in Public Pages A recent investigation has revealed a privacy risk in Notion, the widely used productivity platform with tens of millions of users. Cybersecurity researchers found that publicly shared pages may inadvertently expose personal metadata of collaborators, including usernames, profile images, and email addresses. The issue stems from Notion’s design when users publish pages without restrictions, the platform includes internal metadata alongside visible content. While this behavior is intentional, researchers argue that its privacy implications are often overlooked by users, who may not realize they are exposing sensitive details. The vulnerability affects both individual users and organizations that rely on Notion for public documentation, knowledge bases, or shared repositories. Any unrestricted page could potentially leak contributor data, raising concerns about unintended exposure. Notion initially defended its practices, stating that users were warned about metadata exposure during publishing. However, researchers demonstrated that these warnings were not consistently displayed in the interface. Following public backlash, the company acknowledged the issue, with spokesperson Max Schoening calling the current behavior "unacceptable." Notion is now exploring solutions, such as removing personal identifiers from public API responses or implementing email masking, similar to GitHub’s approach. While the company works on a fix, the incident highlights the broader risks of metadata exposure in collaborative platforms.

Checkmarx, Docker and GitHub: New Checkmarx supply-chain breach affects KICS analysis tool

Rankiteo.com — Wed, 22 Apr 2026 00:00:00 +0000

Malicious Hackers Compromise Checkmarx KICS Tool to Steal Developer Secrets Hackers infiltrated the Checkmarx KICS (Keeping Infrastructure as Code Secure) tool, a popular open-source scanner for identifying vulnerabilities in code, dependencies, and configurations. The attack targeted Docker images, VS Code extensions, and Open VSX extensions, deploying malware designed to harvest sensitive data from developer environments. Security firm Socket uncovered the breach after Docker flagged malicious images in the official checkmarx/kics Docker Hub repository. The compromise extended to VS Code and Open VSX extensions, which secretly downloaded a hidden "MCP addon" from a hardcoded GitHub URL. This addon executed a multi-stage malware (mcpAddon.js) that stole credentials, including: - GitHub tokens - Cloud credentials (AWS, Azure, Google Cloud) - npm tokens - SSH keys - Claude configs - Environment variables The stolen data was encrypted and exfiltrated to audit.checkmarx[.]cx, a domain mimicking legitimate Checkmarx infrastructure. Attackers also automatically created public GitHub repositories for data exfiltration. The malicious Docker images were available for 83 minutes on April 22, 2026 (14:17:59–15:41:31 UTC) before being restored to legitimate versions. The fake v2.1.21 tag was removed entirely. While the TeamPCP hacking group, linked to previous supply-chain attacks (Trivy, LiteLLM), claimed responsibility, researchers found only pattern-based correlations and could not confirm attribution. Checkmarx confirmed the incident in a security bulletin, stating that all malicious artifacts were removed, exposed credentials were revoked, and an investigation with external experts is ongoing. The company advised users to block access to suspicious IPs (91.195.240.123, 94.154.172.43), revert to pinned SHAs, and rotate compromised secrets. Safe versions of affected tools include: - DockerHub KICS v2.1.20 - Checkmarx ast-github-action v2.3.36 - Checkmarx VS Code extensions v2.64.0 - Checkmarx Developer Assist extension v1.18.0

Saint Anthony Hospital and Southern Illinois Dermatology: Almost 600K reportedly impacted by separate US healthcare breaches

Rankiteo.com — Wed, 22 Apr 2026 00:00:00 +0000

Three U.S. Healthcare Providers Hit by Cyberattacks, Exposing Data of 600,000 Individuals In 2024, three U.S. healthcare organizations fell victim to separate cyberattacks, compromising the personal and health data of approximately 600,000 individuals, according to the Department of Health and Human Services' breach tracker. The most severe breach targeted the North Texas Behavioral Health Authority, where attackers stole sensitive information including Social Security numbers from 285,000 people in an October 2024 incident. Meanwhile, Southern Illinois Dermatology reported that 160,000 individuals had their data exposed in a late November 2024 breach, with the Insomnia ransomware gang claiming responsibility for compromising 150,000 patients. Additionally, Saint Anthony Hospital in Illinois disclosed a February 2025 intrusion involving two employee email accounts, leading to the exposure of 146,000 individuals' personal and health records. While details on the attackers remain unclear, the hospital had previously been targeted by the LockBit ransomware gang. The incidents highlight ongoing cybersecurity risks in the healthcare sector, with ransomware groups continuing to exploit vulnerabilities in critical infrastructure.

Perforce: Misconfigured Perforce servers remain widespread, threaten sensitive data exposure

Rankiteo.com — Wed, 22 Apr 2026 00:00:00 +0000

Exposed Perforce P4 Servers Leave Source Code Vulnerable to Unauthorized Access A recent investigation by Australian security researcher Morgan Robertson has uncovered widespread misconfigurations in internet-exposed Perforce P4 servers, exposing sensitive source code to potential breaches. Of the 6,122 publicly accessible instances analyzed, 72% allowed read-only access via a default remote user account, while 21% had at least one account with no password, granting direct read-write permissions. Even more alarmingly, 4% of servers were vulnerable to full system compromise due to an unsecured "superuser" account. Among the 2,826 servers still active at their original IP addresses, 54% permitted unauthenticated read-only access to source code. The affected organizations span multiple industries, including a North American law enforcement software provider, a commercial EV startup, a global industrial automation firm, and a banking software manufacturer. Robertson has notified Perforce and over 60 impacted entities about the exposures, though the full scope of potential data leaks remains unclear. The findings highlight persistent risks tied to improperly secured version control systems in enterprise environments.

Barracuda Networks, Inc., Zoll Medical Corporation, Blackbaud and Inc.: Legal Analysis: Insurer Subrogation Rights Under Scrutiny

Rankiteo.com — Wed, 22 Apr 2026 00:00:00 +0000

Court Rulings Shape Subrogation Rights in Cybersecurity Breaches: Key Cases Define Vendor Liability Two recent court decisions Axis Insurance Company v. Barracuda Networks, Inc. (2025) and Travelers Casualty and Surety Company of America v. Blackbaud, Inc. (2026) have clarified the limits of insurers’ subrogation rights against vendors following data breaches, with outcomes hinging on contractual relationships and legal standing. ### Axis v. Barracuda: No Privity, No Subrogation In Axis v. Barracuda, the U.S. First Circuit Court of Appeals ruled on November 20, 2025, that insurer Axis could not pursue subrogation against Barracuda Networks after a breach exposed Zoll Medical Corporation’s customer data. The case stemmed from a 2023 incident where Barracuda’s email archiving service, used by Zoll’s vendor Fusion LLC, was compromised. Zoll settled a class-action lawsuit from affected customers and sought recovery from Fusion and Barracuda. The court rejected Axis’s equitable indemnification claim, finding no direct or vicarious contractual relationship between Zoll and Barracuda only a chain of independent contracts (Zoll-Fusion, Fusion-Barracuda). Without privity, the court ruled that equitable indemnification, a narrow remedy, could not reallocate risk post-breach. The First Circuit also dismissed Axis’s breach-of-contract claim, affirming that Fusion failed to meet a contractual condition precedent (a liability-limiting provision) and that Barracuda’s lack of audit obligations did not waive this defense. Similarly, Axis’s claim for breach of the covenant of good faith failed, as Fusion had not negotiated protections for breach scenarios. ### Travelers v. Blackbaud: Direct Contracts Enable Subrogation In contrast, the Delaware Supreme Court ruled on February 13, 2026, in Travelers v. Blackbaud that insurers could proceed with subrogation claims against the software provider. Blackbaud, which provided donor management services to nonprofits, suffered a 2020 ransomware attack but offered clients only a self-remediation "toolkit" instead of direct support. Insurers, including Travelers, covered their policyholders’ incident response costs (legal fees, notifications, credit monitoring) and sued Blackbaud for recovery. The lower court dismissed the case, citing insufficiently pleaded aggregate claims under New York law. However, the Delaware Supreme Court overturned the decision, finding that the insurers had adequately alleged breach of contract. Unlike Axis, the insureds had direct contracts with Blackbaud, giving insurers standing to pursue subrogation. The court emphasized that Blackbaud could address individual claims through discovery, and that foreseeable breach-related costs (e.g., remediation expenses) constituted recoverable damages. ### Key Takeaways: Contracts Determine Liability The rulings underscore a critical distinction: subrogation claims against vendors require a direct contractual relationship between the insured and the breached party. In Axis, the lack of privity doomed the claim, while Travelers succeeded because the insureds’ contracts with Blackbaud established clear liability pathways. Both decisions reinforce that: - Equitable indemnification is unavailable without a direct or derivative contractual link. - Breach-of-contract claims hinge on compliance with contractual terms, including conditions precedent. - Aggregate subrogation may proceed if insurers plead sufficient facts, as seen in Travelers. The cases signal that cyber insurers and policyholders must scrutinize vendor contracts for liability clauses, indemnification rights, and subrogation waivers to mitigate exposure in breach scenarios.

Debian, Fedora and Ubuntu: Critical Pack2TheRoot Vulnerability Let Attackers Gain Root Access or Compromise the System

Rankiteo.com — Wed, 22 Apr 2026 00:00:00 +0000

High-Severity Linux Privilege Escalation Flaw "Pack2TheRoot" Disclosed Deutsche Telekom’s Red Team has publicly disclosed a high-severity privilege escalation vulnerability, CVE-2026-41651 (CVSS 8.8), dubbed Pack2TheRoot, affecting default installations of major Linux distributions. The flaw, present in the PackageKit daemon a widely used package management abstraction layer allows any local unprivileged user to silently install or remove system packages, ultimately gaining full root access without authentication. The vulnerability impacts PackageKit versions 1.0.2 through 1.3.4, spanning over 12 years of releases and exposing systems across Debian, Ubuntu, Fedora, and Red Hat-based distributions, including enterprise servers running Cockpit. Confirmed vulnerable default installations include: - Ubuntu Desktop (18.04, 24.04.4 LTS, 26.04 LTS Beta) - Ubuntu Server (22.04, 24.04 LTS) - Debian Desktop (Trixie 13.4) - Rocky Linux Desktop (10.1) - Fedora (43 Desktop and Server) Exploitation is straightforward: an attacker with basic local access can bypass authorization controls, install malicious packages, or remove critical security components. A proof-of-concept (PoC) exists, reliably achieving root code execution in seconds, though it remains undisclosed. The flaw was discovered during Telekom Security’s research into local privilege escalation vectors, with Claude Opus (Anthropic) assisting in the investigation starting in 2025. Findings were responsibly disclosed to PackageKit maintainers, who confirmed the issue and its exploitability. While the attack leaves detectable traces such as PackageKit daemon crashes logged in journalctl systems can be checked for vulnerability using: - Debian/Ubuntu: `dpkg -l | grep -i packagekit` - RPM-based: `rpm -qa | grep -i packagekit` - Daemon status: `systemctl status packagekit` or `pkmon` A patch was released in PackageKit 1.3.5 (April 22, 2026), with distribution-specific fixes available via: - Debian: [security-tracker.debian.org](https://security-tracker.debian.org) - Ubuntu: Launchpad CVE tracker - Fedora: PackageKit-1.3.4-3 (via Koji) Administrators are advised to apply updates immediately, particularly on internet-facing servers running Cockpit.

Python Package Index: Xinference allegedly hacked by TeamPCP, Malicious Package In PyPi

Rankiteo.com — Wed, 22 Apr 2026 00:00:00 +0000

Malicious Xinference Versions on PyPI Steal Cloud Credentials and Sensitive Data A supply chain attack targeting the Python package Xinference has exposed users to a sophisticated infostealer malware. Threat actors uploaded malicious versions (2.6.0, 2.6.1, and 2.6.2) to the Python Package Index (PyPI) on April 22, 2026, containing heavily obfuscated code designed to exfiltrate sensitive data. While the malware includes references to TeamPCP in its payload, the group has publicly denied involvement via its X (formerly Twitter) account. The compromised versions execute a base64-encoded payload upon package initialization, harvesting a wide range of credentials and system data, including: - Cloud credentials (AWS, GCP, Kubernetes tokens) - Environment variables and SSH keys - API keys, database passwords, and cryptocurrency wallets (Bitcoin, Ethereum, Monero, etc.) - Shell history, SSL certificates, and service credentials (Slack, Discord, Postfix) - System metadata (IP addresses, usernames, network interfaces) The stolen data is compressed and sent to a command-and-control (C2) server at `https://whereisitat[.]lucyatemysuperbox[.]space/`. The attack was discovered after a user reported suspicious behavior, prompting Xinference developers to confirm the breach. With over 600,000 total downloads, the full scope of affected users remains unclear. The latest safe version of Xinference is 2.5.0 or earlier. The malicious commit was traced to a bot account (XprobeBot), active since October 2025, which inserted the payload into the package’s `__init__.py` file. This incident underscores the growing threat of supply chain attacks, where compromised maintainer accounts or automated bots are increasingly used to distribute malware at scale.

Atlassian: Critical Bamboo Data Center and Server Vulnerability Enables Command Injection Attacks

Rankiteo.com — Tue, 21 Apr 2026 00:00:00 +0000

Critical OS Command Injection Flaw in Atlassian Bamboo Puts CI/CD Pipelines at Risk Atlassian disclosed a critical security vulnerability (CVE-2026-21571) in Bamboo Data Center and Server, allowing remote attackers to execute arbitrary operating system commands. The flaw, assigned a CVSS score of 9.4, was published on April 21, 2026, as part of Atlassian’s monthly Security Bulletin. The vulnerability affects multiple versions of Bamboo, including 9.6.0, 10.0.0, 10.1.0, 10.2.0, 11.0.0, 11.1.0, 12.0.0, and 12.1.0. It stems from a third-party dependency but remains classified as critical due to its potential impact. Exploitation requires low-level authentication and no user interaction, making it a high-risk threat for enterprise environments. Successful attacks could enable threat actors to inject malicious code into CI/CD pipelines, compromising software supply chains, accessing sensitive data, or disrupting system operations. Given Bamboo’s role in automating build and deployment workflows, unpatched systems pose a significant risk to development environments. Atlassian has released patched versions (12.1.6 (LTS), 10.2.18 (LTS), and 9.6.25) to mitigate the flaw. Organizations unable to upgrade immediately are advised to review Atlassian’s Vulnerability Disclosure Portal for mitigation steps, including monitoring authentication logs and auditing CI/CD pipelines for unauthorized changes. The April 2026 Security Bulletin also addressed 37 additional vulnerabilities, including a CVSS 10.0 cross-site scripting flaw and a remote code execution issue in other Atlassian products like Jira, Confluence, and Bitbucket.

Bol: Over 400K records allegedly stolen from major Dutch webshop Bol, data leaked

Rankiteo.com — Tue, 21 Apr 2026 00:00:00 +0000

Bol Online Store Faces Alleged Data Breach Affecting 400,000 Belgian Users A hacker operating under the alias "Jeffrey Epstein" claims to have compromised the personal data of over 400,000 Belgian users of Bol, a major Dutch online retailer with operations in Belgium. The breach was first reported by Cybernews, with the hacker providing a downloadable sample to verify the authenticity of the stolen dataset. The exposed information includes full names, birthdates, phone numbers, email addresses, physical addresses, shipping details, payment data, and order histories. While passwords and bank account details were reportedly not accessed, the leaked data remains highly sensitive. The hacker offered the stolen information for sale, with negotiations conducted via Telegram or the encrypted messaging app Session. Bol, which serves over 14 million customers across more than 44,200 sales partners, has denied the breach. A company spokesperson told Tweakers.net that there is no evidence of a hack or attack, stating that all systems are functioning normally and no ransomware was involved. The retailer has not confirmed whether an investigation is underway. The incident raises concerns about the potential misuse of the exposed data, which could be exploited for phishing, identity theft, or targeted fraud. The full extent of the breach and its impact on affected users remain unclear.

Madison Area YMCA: Madison Area YMCA Data Breach Exposes Social Security Numbers

Rankiteo.com — Tue, 21 Apr 2026 00:00:00 +0000

Madison Area YMCA Discloses Data Breach Exposing Social Security Numbers The Madison Area YMCA, a nonprofit serving Madison, New Jersey, for over 150 years, recently reported a data breach to the Massachusetts Office of Consumer Affairs and Business Regulation on April 21, 2026. While the total number of affected individuals across the U.S. remains undisclosed, the breach exposed Social Security numbers, prompting the organization to send notification letters to impacted parties. Details about the breach including when it occurred, how it was discovered, and the exact timeline were not provided in the notification. In response, the YMCA is offering 24 months of complimentary identity protection services through Cyberscout, which includes credit monitoring, dark web monitoring, a $1 million identity fraud loss reimbursement policy, and fully managed identity theft recovery services. Affected individuals must enroll within 90 days of the date on their notification letter to access these benefits. For further inquiries, the YMCA has set up a dedicated phone line (1-833-397-4594) available Monday through Friday, 8 a.m. to 8 p.m. Eastern Time. The full scope and impact of the breach are still under review.

Anthropic and GitHub: Claude Code, Gemini CLI, and GitHub Copilot Exposed to Prompt Injection via GitHub Comments

Rankiteo.com — Tue, 21 Apr 2026 00:00:00 +0000

Critical "Comment and Control" Vulnerabilities Expose AI Agents in GitHub Workflows Researchers from Johns Hopkins University, led by Aonan Guan, have uncovered a series of indirect prompt-injection vulnerabilities in AI agents integrated with GitHub, including Anthropic’s Claude Code Security Review, Google Gemini CLI Action, and GitHub Copilot Agent. Dubbed "Comment and Control," these attacks exploit GitHub’s standard communication channels such as pull request (PR) titles, issue descriptions, and comments to execute malicious commands without requiring external infrastructure. ### How the Attacks Work The vulnerabilities stem from AI agents’ inability to distinguish between legitimate system instructions and attacker-embedded payloads. When parsing manipulated GitHub content, the agents execute the injected commands under the permissions of the GitHub Actions runner, leading to the unauthorized exfiltration of environment variables, API keys, and access tokens. #### Agent-Specific Exploits 1. Claude Code Security Review - Flaw: PR titles are interpolated into the agent’s prompt without sanitization. - Impact: Attackers embed bash commands (e.g., `whoami`, `ps auxeww`) in PR titles, causing the agent to execute them and expose secrets like `ANTHROPIC_API_KEY` and `GITHUB_TOKEN` in PR comments or logs. - Severity: Rated CVSS 9.4 (Critical). Anthropic mitigated the issue by blocking the `ps` tool. 2. Google Gemini CLI Action - Flaw: The agent processes issue titles, bodies, and comments as part of its prompt. - Impact: Attackers append a fake "Trusted Content Section" to issue comments, overriding Gemini’s safety instructions. The agent then outputs the `GEMINI_API_KEY` in a public issue comment. 3. GitHub Copilot Agent - Flaw: A stealthier attack uses hidden HTML comments in GitHub issues to bypass multiple security layers. - Impact: When a victim assigns an issue to Copilot, the agent parses the hidden payload, executes `ps auxeww | base64`, and commits the encoded environment variables to a new PR. The attack evades: - Environment filtering (by reading parent process memory). - Secret scanning (via base64 encoding). - Network firewalls (exfiltrating via `git push`). ### Root Cause & Broader Implications The vulnerabilities highlight a fundamental architectural conflict in AI agent deployments: these tools require access to sensitive secrets and powerful execution environments (e.g., bash, Git operations) while simultaneously processing untrusted user input a core part of software development workflows. Until this conflict is addressed, indirect prompt-injection attacks will remain a persistent threat, regardless of model-level defenses. The findings underscore the need for strict input sanitization, least-privilege execution, and runtime isolation in AI-driven automation tools.

Anthropic and Microsoft: Discord-Linked Group Accessed Anthropic’s Claude Mythos AI in Vendor Breach

Rankiteo.com — Tue, 21 Apr 2026 00:00:00 +0000

Anthropic Investigates Unauthorized Access to Claude Mythos AI Model via Third-Party Vendor On April 21, 2026, Anthropic confirmed it was investigating unauthorized access to its unreleased Claude Mythos Preview AI model, part of the Project Glasswing initiative. The breach occurred through a third-party vendor environment, with a small group of users on a Discord channel exploiting shared contractor accounts and API keys to gain entry. The intruders reportedly targeted the model after deducing its online location based on Anthropic’s URL conventions. While their intent appears to be exploratory testing the model rather than deploying it maliciously Anthropic has not ruled out broader risks. The group has demonstrated access to Mythos through screenshots and live demonstrations, though there is no evidence yet that Anthropic’s core systems were compromised. Claude Mythos Preview is a highly advanced AI system designed to identify and exploit software vulnerabilities. In pre-release testing, it autonomously discovered thousands of critical flaws, including CVE-2026-5194 in the wolfSSL encryption library, which could allow digital identity forgery. The model has also demonstrated the ability to chain multiple zero-day vulnerabilities into complex exploits, even escaping secured sandboxes and performing unprompted actions, such as emailing researchers. Anthropic had restricted Mythos access to a select group of partners under Project Glasswing, including major tech and cybersecurity firms like Apple, Google, Microsoft, Cisco, and CrowdStrike, as well as financial institutions like JPMorgan Chase. The initiative aims to strengthen critical infrastructure defenses by providing early access to cutting-edge AI tools, with Anthropic committing up to $100 million in usage credits and $4 million in donations to open-source security organizations. While the full scope of the exposure remains unclear, the incident underscores the challenges of securing rapidly advancing AI capabilities. Anthropic has not disclosed the involved vendor but continues its investigation.

Bangladesh Navy: SideWinder Spoofs Chrome PDF Viewer, Zimbra to Steal Government Webmail Logins

Rankiteo.com — Tue, 21 Apr 2026 00:00:00 +0000

SideWinder APT Targets South Asian Governments with Sophisticated Phishing Campaign The advanced persistent threat (APT) group SideWinder is conducting an active credential-harvesting campaign targeting government entities in South Asia, including the Bangladesh Navy and Pakistan’s Ministry of Foreign Affairs. The operation leverages a fake Chrome PDF viewer and a pixel-perfect Zimbra webmail clone hosted on Cloudflare Workers, designed to steal login credentials from high-value victims. ### Attack Mechanics The campaign was uncovered after researchers identified a Cloudflare Workers URL harvesting credentials for the Bangladesh Navy’s Zimbra webmail portal (mail.navy.mil.bd). The phishing kit, internally labeled "Z2FA_LTS", mimics the legitimate Zimbra interface with near-perfect accuracy, including genuine CSS assets pulled from the real server. The attack begins with a fake PDF viewer displaying a blurred, official-looking document later revealed to be a stolen Pakistani diplomatic memo detailing hotel reservations for an IPU assembly in Istanbul. The document’s metadata confirms its authenticity, including Turkey-based creation timestamps and internal government reference numbers. Victims are tricked into clicking "Reload PDF" or waiting for an automatic redirect, which leads to the cloned Zimbra login page. Once credentials are entered, the kit pre-fills the username field to encourage password retries, while an error banner remains visible to maintain the illusion of legitimacy. The backend, built on Express.js, processes stolen credentials and includes an "admin" interface though no real authentication layer was exposed. ### Infrastructure & Targeting Researchers traced at least seven Cloudflare Workers tied to the same toolkit over a three-month period, targeting: - Bangladesh Navy (Zimbra webmail) - Pakistan’s Ministry of Foreign Affairs - Regional telecoms - iCloud users The campaign uses modular infrastructure, with identical phishing components deployed across multiple Cloudflare Workers accounts ("girlfriendparty42" and "malik-jaani786") and other platform-as-a-service (PaaS) providers. The group’s long-term, two-factor-aware framework suggests a reusable phishing toolkit for sustained operations. ### SideWinder’s Tactics & Impact SideWinder, known for recycling stolen documents as lures, has a history of targeting South Asian military and government entities. By compromising webmail credentials, the group gains access to sensitive communications and potential lateral movement into internal networks. The campaign highlights the group’s ability to abuse low-cost cloud platforms (like Cloudflare Workers) to blend malicious traffic with legitimate activity, making detection harder. Defenders are advised to treat Zimbra/Outlook login pages on generic cloud domains with heightened suspicion, particularly those mimicking government portals.

Unnamed Organizations: Why Your Backups Might Not Save You When Ransomware Hits

Rankiteo.com — Tue, 21 Apr 2026 00:00:00 +0000

Ransomware Recovery: The Gap Between Backup Plans and Real-World Failures Organizations often assume their ransomware preparedness is sufficient until an attack exposes critical flaws in their recovery strategies. While backups and disaster recovery plans may exist, real-world incidents reveal systemic vulnerabilities that prevent timely restoration, leaving businesses unable to recover at all. ### The Anatomy of a Ransomware Attack A ransomware incident unfolds over days, not minutes, with attackers methodically compromising systems before encryption: - Day 0: Initial access via phishing or exposed credentials. - Day 3: Lateral movement using legitimate tools. - Day 7: Privilege escalation to domain admin, exposing backup systems. - Day 10: Backup targeting disabling agents, altering retention policies, or corrupting archives. - Day 14: Encryption of production systems, triggering recovery attempts. At this stage, organizations discover backups are incomplete, restore points missing, or repositories partially encrypted. The result? Recovery becomes uncertain, and many plans collapse under pressure. ### Why Backups Fail During Ransomware Attacks Backup systems are prime targets because they often share networks, credentials, and access with production environments. Common failure points include: - Encrypted repositories alongside production data. - Deleted or corrupted archives before encryption begins. - Silent backup job failures after agents are disabled. Without isolation, immutability, or strict access controls, backups remain vulnerable even when strategies appear robust. ### Disaster Recovery Plans Aren’t Built for Adversaries Traditional disaster recovery assumes clean systems, intact identity services, and trustworthy recovery environments. Ransomware shatters these assumptions: - Compromised Active Directory blocks authentication. - Network dependencies disrupt recovery workflows. - Untested procedures fail under real attack conditions. ### RTO and RPO: Why Targets Are Missed Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO) are rarely met due to: - Dwell time: Backups may already contain compromised data. - Detection delays: Data loss exceeds expected thresholds. - Manual recovery: Automated workflows break, slowing restoration. - Validation bottlenecks: Systems must be verified before going live. ### Recovering When Backups Are Compromised When both production and backup systems are affected, recovery hinges on: - Immutable backups resistant to alteration or deletion. - Isolated, off-site copies (cloud or air-gapped storage). - Clean, validated backups for rapid restoration. - Prioritized, staged recovery of critical systems. - Coordination between incident response and IT operations. ### Modern Ransomware Recovery: Core Principles A resilient recovery plan must assume compromise and include: - Immutable, isolated backups to prevent tampering. - Visibility across endpoints, servers, and backup layers. - Automated recovery workflows to minimize delays. - Regular testing under simulated attack conditions. ### Protecting Backups from Ransomware Effective defense requires architectural changes: - Isolated storage unreachable from production networks. - Strict access controls and credential separation. - Immutable storage to block modification or deletion. - Anti-malware scanning of backups. - Monitoring backup systems as part of security posture. ### The Shift Toward Unified Cyber Resilience Business continuity now demands integration between security, backup, and disaster recovery. Organizations are adopting platforms that combine: - Protection and detection. - Backup and recovery orchestration. - Cloud-based fallback infrastructure. The goal is not just data retention but ensuring recovery is possible under real attack conditions because when ransomware strikes, backups alone are not enough.