data breaches
Activision Pulls Call of Duty: WWII from Microsoft Store After Players Hacked

Activision has been forced to take down the Microsoft Store version of Call of Duty: WWII after players began reporting serious cybersecurity incidents tied to the game’s PC build. The 2017 title, recently relaunched on Game Pass, was exploited by malicious actors who used a previously undisclosed flaw to gain remote access to players’ machines, leading to a rare but impactful shutdown of a major online game.
The takedown highlights growing concerns in the gaming industry about client-side vulnerabilities, supply chain risks, and the consequences of understaffed cybersecurity teams at major studios.
Activision’s Statement and Action
While Activision has not released detailed technical findings, the company confirmed in a brief announcement that it had “temporarily disabled access to the Microsoft Store build of Call of Duty: WWII to investigate a security vulnerability impacting some players on PC.”
The vulnerability reportedly allowed attackers to use compromised lobbies or peer-to-peer game traffic to deliver malicious payloads, potentially leveraging code injection or DLL sideloading techniques commonly seen in game hacking and modding communities.
Technical Breakdown: Possible Exploit Vectors
Based on independent research and prior case patterns in multiplayer gaming environments, several likely vectors are being investigated by the cybersecurity community:
1. Remote Code Execution via Modded Lobbies
Mechanism: Attackers may have hosted or injected into custom game lobbies where malicious scripts or modified game logic could be pushed to connected clients.
Risk: Once a player joined, arbitrary code could be executed locally under the same privileges as the game process.
2. DLL Injection via Game Mod Loaders
Mechanism: The PC version may have lacked proper signature verification or binary integrity checks, allowing attackers to inject custom DLLs that executed upon game launch.
Risk: These DLLs could serve as backdoors or dropper payloads for larger malware frameworks.
3. Peer-to-Peer (P2P) Packet Exploits
Mechanism: Older versions of CoD games use P2P networking for multiplayer. An attacker could send crafted UDP packets that triggered buffer overflows or memory corruption in the game’s network handling code.
Risk: Exploits could hijack client memory, allowing attackers to execute code or crash systems remotely.
4. Supply Chain Misconfiguration
Mechanism: The version distributed via Microsoft Store/Game Pass might have had unpatched legacy libraries or a misconfigured update pipeline.
Risk: Attackers could abuse overlooked dependencies (e.g., outdated DirectX components or input libraries) to trigger local privilege escalation or code execution.
Impact and Industry Fallout
The issue is particularly sensitive given that the title was newly added to Microsoft Game Pass, putting it in front of thousands of unsuspecting players—many of whom may not have enabled robust endpoint protections.
“This is a textbook example of why legacy titles need just as much security investment as live-service games,” said a former developer on Activision’s anti-cheat team.
Activision’s Security History and Response
The incident comes at a time when Activision has faced multiple rounds of layoffs, some of which impacted its cybersecurity and anti-cheat divisions. Industry insiders report that several experienced infosec engineers were cut in early 2024 as part of cost-reduction efforts.
By contrast, other publishers such as Riot Games, Ubisoft, and Epic Games have ramped up internal cybersecurity hiring, threat modeling, and real-time telemetry systems in response to a rise in targeted game-based exploits.
What Happens Next?
- The Microsoft Store version of CoD: WWII remains offline pending investigation.
- No confirmation yet if players will receive security patches or credit for downtime.
- Activision is expected to publish a CVE bulletin or threat advisory if the issue involves system-level risk.
Key Lessons for the Gaming Industry
- Legacy code must be actively audited before being redistributed.
- Peer-to-peer multiplayer networking is inherently risky in 2025.
- Layoffs affecting security staff can have long-term operational consequences.
If confirmed, this will be one of the few known instances where a triple-A video game has been delisted due to real-world cyberattacks on its player base.
data breaches
Exposed: The Cybersecurity Fails Behind This Week’s Most Alarming Hacks

In a week marked by coordinated arrests, evolving malware, and exposed infrastructure, the cybersecurity world once again proved that no system—no matter how secured, encrypted, or modernized—is beyond reach. From luxury retailers to connected vehicles and national firewalls, attackers demonstrated sophistication, while defenders scrambled to patch, detect, and respond.
Yet amid the growing volume of threats, what stood out most was the precision of these campaigns: calculated attacks exploiting overlooked configurations, trusted components, or insecure-by-design systems. And the message from the underground was clear—technical skill is evolving faster than most defense budgets.
“These are no longer lone actors in basements. This is organized, multi-vector, and sometimes nation-linked digital warfare.”
— Shah Sheikh, Former Global Threat Advisor, BT Security
A Week of Tactical Breaches and Digital Leverage
This week’s headlines spanned five continents and every layer of the attack surface:
🕷️ Scattered Spider arrests across the U.K.
🚗 Bluetooth-based remote car hacks
🍏 Stealthy macOS malware using Windows-style injection
🛡️ Critical Fortinet FortiWeb RCE flaw with public PoC
🧪 GitHub and Laravel key leaks exposing entire stacks
At the center of it all? A simple truth: the more we connect, the more we expose.
Scattered Spider: A Digital Gang Built on Access
In a coordinated operation, British law enforcement arrested four individuals linked to the hacker collective Scattered Spider, a group infamous for SIM swapping, ransomware extortion, and social engineering against tech and retail giants. Victims include household names like Harrods, Co-op, and Marks & Spencer.
Operating under the alias “The Com,” the group leveraged deep reconnaissance and identity manipulation to gain initial access—often via weak MFA implementations or internal staff credentials purchased on dark web forums.
“These guys understood corporate psychology as well as they understood code.”
— Mike Yates, Insider Threat Consultant
PerfektBlue: A Critical Hit on Cars
Security researchers revealed PerfektBlue, a chained Bluetooth exploit targeting OpenSynergy’s Blue SDK, a library embedded in infotainment systems from automakers including Mercedes-Benz, Volkswagen, and Škoda. The flaws allow for remote code execution (RCE) over Bluetooth if a device is in discoverable mode.
At the heart of the attack: heap corruption vulnerabilities that bypass memory safety checks in low-level firmware.
“This is the modern CAN bus threat: you don’t need to touch the car to compromise it.”
— Anya Plichta, Automotive Reverse Engineer
macOS: The Quiet Rise of Stealth Malware
Long considered more secure by design, macOS faced an aggressive wave of trojanized SSH clients and fileless backdoors this week. Researchers observed malware hiding in modified versions of Termius and other developer tools—using process injection to mask its activity and exfiltrate SSH keys and tokens over encrypted TLS channels.
Apple’s XProtect was blind to the initial binaries. The persistence mechanism relied on launchd plists, granting attackers stealth and root-level persistence.
Fortinet FortiWeb RCE: CVE-2025-25257
Fortinet issued an emergency patch for a critical SQL injection flaw in its web application firewall appliance, FortiWeb. Rated 9.6 CVSS, the vulnerability allowed attackers to inject payloads through Bearer token headers, leading to unauthenticated RCE via crafted HTTP requests.
Exploitation was trivial—and a proof-of-concept was already circulating privately on Telegram within hours of disclosure.
“SQLi in 2025 is the same as it was in 2005—except now it hits your firewall.”
— Rachel Cohen, Cloud Security Engineer
Development Pipelines: Laravel Leaks and Red-Team Reuse
GitHub repos revealed over 600 misconfigured Laravel apps leaking APP_KEY
secrets—enabling attackers to decrypt session cookies, forge tokens, and potentially trigger remote code execution in Laravel-based environments.
Meanwhile, malware analysts flagged the re-emergence of Shellter, a legitimate red-team tool, now repurposed to inject stealer payloads into enterprise-ready EXEs. Once again, security tools are being flipped into weapons—this time against those who trust them most.
A Week That Redefined the Attack Surface
In just seven days, attackers compromised retailers, cars, firewalls, developers, and trust. The attack vectors weren’t new—but the orchestration was cleaner, faster, and more deeply integrated than ever.
“The edge is gone. You either build for breach resilience, or you’re already owned.”
— Erik Boucher, Red Team Leader, BreachCore
Conclusion: The Code Is Only as Secure as the Context
This week’s wave of attacks reminds us that software is never neutral. Every API, every token, every Bluetooth interface and CLI tool holds the potential for exploitation if misunderstood or under-defended.
The modern adversary isn’t loud. They’re layered, they’re embedded, and they’re already moving laterally while you’re still investigating login anomalies.
Stay patched. Stay paranoid. Stay persistent.
business
Louis Vuitton Confirms U.K. Customer Data Breach in Latest Cyberattack

In a troubling sign for luxury retail cybersecurity, Louis Vuitton has confirmed a data breach that compromised personal information belonging to customers in the United Kingdom. The cyberattack, which occurred on July 2, 2025, marks the third known incident targeting LVMH systems in the past three months.
The breach exposed sensitive details such as customer names, contact information, and purchase history, according to a statement released by the company.
“This incident is deeply regrettable. We are fully cooperating with the authorities and have taken immediate steps to contain the breach,”
— Louis Vuitton spokesperson
Pattern of Global Exposure
This latest breach follows a similar cyberattack on Louis Vuitton’s South Korean operations, further raising concerns about the cybersecurity posture of luxury conglomerate LVMH (Moët Hennessy Louis Vuitton).
“The nature of these attacks underscores the evolving threat landscape facing global retailers. No brand—no matter how prestigious—is immune,”
— Marc Delattre, Cybersecurity Analyst
Regulatory Response and Next Steps
Louis Vuitton has formally notified the U.K. Information Commissioner’s Office (ICO) and launched an internal investigation. Under GDPR, companies are required to notify both regulators and affected customers when a breach presents a high risk to individual privacy.
“We are conducting a preliminary review and expect the company to keep affected individuals informed,”
— ICO Spokesperson
LVMH stated that it is taking further measures to strengthen cybersecurity controls, and ensure such incidents are not repeated.
What You Can Do if You’re Affected
Customers in the U.K. who have recently interacted with Louis Vuitton are advised to:
- Monitor emails for breach notification
- Be cautious of phishing attempts
- Review any suspicious account activity
- Contact Louis Vuitton support for confirmation and support
data breaches
Terrifying New Ransomware Surge: Iranian Hackers Behind Pay2Key Target Middle East Tech Giants—Act Now to Stay Safe

A cyberespionage group with strong ties to the Iranian state has reemerged, targeting multiple organizations across the Middle East using an enhanced variant of the Pay2Key ransomware. According to recent threat intelligence shared by Check Point Research and corroborated by Israeli CERT, the new wave of attacks includes data theft, wiper components, and credential harvesting, suggesting an evolution beyond classic ransomware-for-profit motives.
Threat Actor Profile: Pay2Key
Pay2Key first surfaced in late 2020, known for ransomware attacks against Israeli firms. While earlier variants focused on fast encryption and ransom notes dropped across corporate environments, recent activity ties the group directly to Iranian threat actor clusters affiliated with APT39 and Agrius.
The group is now believed to be part of Tehran’s broader cyber-espionage apparatus, using ransomware as both a smokescreen and a disruptive geopolitical weapon.
Technical Details of the Attack Chain
The recent campaign exhibits a high level of tactical sophistication:
1. Initial Access
- Exploited public-facing VPN services and unpatched Microsoft Exchange servers
- In some cases, brute-force attacks on remote desktop services (RDP) were successful due to weak credentials
2. Credential Dumping and Lateral Movement
- Deployed Mimikatz and custom LSASS scrapers to extract credentials
- Used PsExec, WMI, and SMB to propagate across the network
3. Payload Deployment
- The updated Pay2Key binary is packed with UPX and uses AES-256 encryption
- Ransom note includes references to “Zionist collaborators” and demands payments in Monero (XMR), a privacy coin harder to trace than Bitcoin
4. Exfiltration and Destruction
- Files exfiltrated via Mega.io API or command-and-control (C2) servers hosted in Russia and Turkey
- In some cases, wiper modules were deployed post-encryption, designed to destroy shadow copies and render recovery impossible
Attribution and Geopolitical Implications
Researchers attribute the campaign to Iranian-backed actors based on:
- Code reuse from prior Agrius malware families
- IP infrastructure historically linked to APT39
- Political messaging within ransom notes
Israeli cybersecurity agencies believe the attack is part of a broader campaign to destabilize regional tech and financial sectors, rather than a simple financial crime. This hybrid of cybercrime and cyberwarfare further blurs attribution lines and complicates international response.
Indicators of Compromise (IOCs)
- IP addresses:
185.220.101.1
,213.108.105.12
- SHA256 Hash:
a92fe9be6f4c1c72e935dbf6f...
- Domains:
command-center[.]xyz
,megasend[.]host
- Ransom Note Filename:
PAY_OR_ELSE.txt
Security teams should monitor traffic for outbound connections to these IOCs and block suspicious DNS resolutions and exfiltration channels.
Mitigation Recommendations
- Patch Microsoft Exchange and Fortinet VPNs immediately
- Implement strict RDP controls and MFA on all remote services
- Segment internal networks and disable lateral movement tools
- Backup critical systems offline; validate restore procedures regularly
- Deploy EDR/XDR solutions capable of detecting fileless or lateral attacks
Expert Quote
“This isn’t just ransomware. It’s cyberwarfare disguised as extortion,” said Amir Sadoughi, a senior threat researcher at Tel Aviv-based CyberDome. “The Pay2Key group is deploying a multi-purpose toolkit that aims to destroy, not profit.”
Conclusion
The return of Pay2Key signals an escalation in the use of ransomware as a geopolitical tool, especially in regions under rising cyber tension. Organizations in the Middle East and allied tech sectors must heighten threat hunting efforts and ensure IR (incident response) readiness.
-
data breaches11 months ago
Ransomware Attack Disrupts Change Healthcare Service
-
Blog11 months ago
Zimbabwe’s Drought Crisis: A Nation on the Brink
-
sports11 months ago
Fiorentina Bolsters Squad with Moroccan Star Richardson
-
Blog11 months ago
Plex Data Breach Exposes Personal Information of Users
-
sports11 months ago
Moroccan-Linked Fake Artisan Mafia Network Scams Over 1,000 Victims in Switzerland
-
politics11 months ago
Political Turmoil in Bangladesh: The Fall of Sheikh Hasina’s Government
-
Blog11 months ago
X Tech Mobile: A Cautionary Perspective on Upgrading Your iPhone
-
Blog11 months ago
Indian Council of Medical Research Data Breach Exposes Health Data of Millions