Connect with us

CyberSecurity

Sweden blames Russian hackers for attempted ‘destructive’ cyberattack on thermal power plant

Published

on

Sweden blames Russian hackers for attempted ‘destructive’ cyberattack on thermal power plant

Swedish authorities have accused Russian state-linked hackers of trying to launch a destructive cyberattack against a thermal power plant in early 2025. The attack ultimately failed, but officials warn that hybrid warfare tactics — blending digital intrusions with physical threats — are becoming more aggressive across Europe.

Carl-Oskar Bohlin, Sweden’s minister of civil defense, revealed the incident during a press conference on Wednesday. He attributed the attempted breach to hackers with ties to Russian intelligence and security services. While the plant was not named, Bohlin confirmed that the attack was thwarted by a built-in protection mechanism.

“Pro-Russian groups that once carried out denial-of-service attacks are now attempting destructive cyber attacks against organizations in Europe,” Bohlin said, as quoted by Bloomberg.

This case underscores a worrying shift: hackers no longer aim merely to disrupt websites or steal data. Instead, they are targeting critical infrastructure — energy grids, water systems, and industrial controls — with the goal of causing real-world damage.

How the Swedish thermal plant attack unfolded

According to Bohlin, the attempted intrusion occurred in early 2025. The hackers tried to compromise operational technology systems at the thermal plant, which generates heat and electricity for local communities. Fortunately, the plant’s safety systems blocked the attack before any physical damage or service disruption occurred.

Bohlin described the behavior as “riskier and more reckless” than previous cyber operations linked to Russia. He did not provide technical details, but cybersecurity experts note that targeting industrial control systems requires significant skill and preparation — and carries a high risk of unintended consequences.

“This is not a random script-kiddie operation,” said a senior European cybersecurity official who spoke on condition of anonymity. “These are state-backed actors with clear intent to cause harm.”

The Swedish government has not released evidence publicly, but the attribution aligns with patterns observed by intelligence agencies across NATO countries.

Rising wave of Russian-linked attacks on critical infrastructure

The Swedish incident fits a broader pattern of Russian-linked cyberattacks against energy and water infrastructure. In December 2024, Russia was accused of attempting to destabilize parts of Poland’s power grid. Earlier that year, hackers briefly hijacked a dam in Norway, opening floodgates that released millions of gallons of water before being expelled from the system.

In Ukraine, the impact has been even more direct. A cyberattack on a municipal energy company in Lviv in January 2024 left hundreds of apartments without heat for two days during freezing temperatures. Researchers found evidence pointing to Russian hackers, though attribution could not be fully confirmed.

These attacks echo the 2015 power grid blackout in Ukraine, which was widely attributed to Russian state-sponsored hackers. That incident cut electricity to hundreds of thousands of people and remains a benchmark for cyber-physical threats.

Hybrid warfare: blending digital and physical threats

Sweden’s civil defense minister emphasized that hybrid attacks — those that extend beyond cyberspace and into the physical world — are becoming more dangerous. The line between cyber espionage and sabotage is blurring, forcing governments to rethink their defense strategies.

“This is not just about data breaches anymore,” Bohlin said. “It is about protecting the systems that keep our society running.”

European nations are now investing heavily in cyber resilience for critical infrastructure. Sweden, for example, has strengthened its cyber defense capabilities and is working closely with NATO allies to share threat intelligence.

Russia’s response and international reaction

A spokesperson for the Russian government did not respond to requests for comment from TechCrunch. Moscow has consistently denied involvement in cyberattacks against Western targets, despite extensive evidence from intelligence agencies and cybersecurity firms.

Nevertheless, the Swedish attribution is likely to increase diplomatic pressure on Russia. The European Union has already imposed sanctions on individuals and entities linked to cyber operations against member states. Further sanctions could target Russian intelligence units responsible for industrial control system attacks.

In the meantime, cybersecurity experts urge critical infrastructure operators to implement robust segmentation, network monitoring, and offline safety mechanisms — the kind of protection that saved Sweden’s thermal plant.

What this means for the future of European security

The attempted attack on Sweden’s thermal plant is a stark reminder that no country is immune. As hybrid warfare tactics evolve, the risk of a successful destructive cyberattack on critical infrastructure remains high.

Governments must move beyond traditional cybersecurity and adopt a whole-of-society approach. This includes public-private partnerships, regular penetration testing, and public awareness campaigns. Protecting critical infrastructure is no longer just an IT issue — it is a national security priority.

“We are seeing a new era of conflict,” Bohlin warned. “One where a hacker in a basement can cause a power outage, a flood, or worse. We must be prepared.”

For now, Sweden’s thermal plant remains operational. But the question lingers: what happens next time the protection mechanism fails?

Continue Reading
Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

CyberSecurity

Critical Ninja Forms Vulnerability Puts Thousands of WordPress Sites at Risk

Published

on

Critical Ninja Forms Vulnerability Puts Thousands of WordPress Sites at Risk

A severe security flaw has been discovered in the Ninja Forms – File Upload Plugin, a popular tool used by millions of WordPress websites. This Ninja Forms vulnerability allows unauthenticated attackers to upload arbitrary files, potentially leading to full site compromise. Security experts are urging administrators to apply the latest patch immediately.

According to researchers at Wordfence, the vulnerability carries a CVSS score of 9.8, marking it as critical. The issue affects all versions of the plugin up to 3.3.26, leaving a vast number of sites exposed to remote code execution (RCE). Attackers can exploit this flaw without needing any authentication, making it a prime target for malicious actors.

How the Ninja Forms Vulnerability Works

The root cause of this WordPress file upload vulnerability lies in insufficient validation during the file upload process. While the plugin includes some checks, they fail to properly verify file types and extensions. This oversight allows attackers to bypass restrictions and upload files with dangerous extensions, such as .php.

Building on this, attackers can manipulate filenames to sidestep existing safeguards. They can also use path traversal techniques to place malicious files in sensitive directories. Once uploaded, these files can execute arbitrary code on the server, often deploying webshells that grant persistent access.

Security researcher Sélim Lanouar, known as whattheslime, discovered the flaw and reported it via the Wordfence Bug Bounty Program. He received a $2,145 reward for his finding. The researcher demonstrated that the attack vector is straightforward, requiring no advanced skills to exploit.

Potential Impact on WordPress Sites

This remote code execution WordPress vulnerability could have devastating consequences for site owners. Attackers gaining control of a website can steal sensitive data, inject malware, redirect visitors to malicious sites, or even take down the entire server. For e-commerce sites, this could mean compromised customer payment information.

Moreover, affected sites can become part of larger botnets or serve as launching pads for attacks on other systems. The ease of exploitation amplifies the risk, as automated scripts can scan for vulnerable installations and deploy payloads at scale.

Wordfence confirmed the proof-of-concept exploit shortly after receiving the report on January 8, 2026. “We validated the report and confirmed the proof-of-concept [PoC] exploit,” the team stated in an advisory. The plugin developer responded with a partial fix on February 10, followed by a complete patch on March 19 with version 3.3.27.

Steps to Protect Your WordPress Site

Administrators must update the Ninja Forms plugin to version 3.3.27 or later immediately. Delaying this patch leaves sites vulnerable, especially given that the attack requires no authentication. Regular security audits and monitoring can help detect unusual file uploads or suspicious activity.

Additionally, consider implementing a web application firewall (WAF) to block malicious upload attempts. Hardening your WordPress installation by restricting file permissions and disabling unused plugins can further reduce risk. For sites handling sensitive data, enabling two-factor authentication for admin accounts adds another layer of defense.

Conclusion

The Ninja Forms vulnerability highlights the ongoing challenges in securing widely-used plugins. As WordPress remains a prime target for attackers, staying up-to-date with patches is non-negotiable. Site owners should act now to apply the fix and safeguard their digital assets from potential compromise.

Continue Reading

CyberSecurity

Adobe releases critical patch for PDF zero-day bug exploited for months by hackers

Published

on

Adobe patches PDF zero-day vulnerability exploited for months by hackers

Adobe has released an urgent security update for its widely-used PDF software, Acrobat and Reader, to fix a critical vulnerability that hackers have been actively exploiting for at least four months. The flaw, tracked as CVE-2026-34621, allows attackers to remotely install malware on a victim’s device simply by tricking them into opening a maliciously crafted PDF file on Windows or macOS. This is a classic PDF zero-day vulnerability that was being used in the wild before Adobe could develop a patch.

According to Adobe’s advisory, the bug affects Acrobat DC, Reader DC, and Acrobat 2024. The company confirmed it is aware of active exploitation, meaning hackers have been leveraging this weakness to break into computers worldwide. While the full scale of the campaign remains unknown, the ubiquity of Adobe’s PDF software makes it a prime target for both cybercriminals and state-sponsored hackers.

How the PDF zero-day vulnerability was discovered

Security researcher Haifei Li, founder of the exploit-detection platform EXPMON, uncovered the CVE-2026-34621 exploit after a malicious PDF was uploaded to his malware scanner. In a detailed blog post, Li revealed that another copy of the same malicious file first appeared on VirusTotal, a popular online malware analysis service, as early as late November 2025. This timeline indicates that attackers had been using the PDF zero-day vulnerability for months before Adobe’s patch.

Li’s analysis showed that opening the poisoned PDF could give the attacker full control over the victim’s system. “This could lead to full control of the victim’s system,” Li wrote, adding that the hacker could then steal a wide range of sensitive data. Unfortunately, it remains unclear who is behind the campaign or what specific targets were chosen, as Li could not retrieve additional exploits from the attacker’s servers.

Why this Adobe security patch matters for users

This Adobe security patch is critical because PDF files are exchanged daily across industries—from legal contracts to academic papers. A malicious PDF malware attack can infiltrate even well-protected networks if a user unknowingly opens a booby-trapped document. The zero-day attack Adobe faced here underscores the persistent threat to widely deployed software.

Adobe has urged all users of Acrobat DC, Reader DC, and Acrobat 2024 to update their software immediately to the latest versions. The patch is available through the software’s automatic update mechanism or via the Adobe website. For enterprise environments, IT administrators should prioritize this update to mitigate the risk of Acrobat Reader bug exploitation.

Protecting against future PDF exploits

Beyond applying the latest patch, users can adopt safer practices to reduce exposure to similar threats. Always verify the source of PDF files before opening them, especially if they arrive unexpectedly via email or downloads. Consider using built-in security features like Adobe’s Protected View, which opens PDFs in a sandboxed environment to limit potential damage.

Security experts also recommend using dedicated PDF readers with enhanced security controls or enabling automatic updates across all software. For organizations, deploying endpoint detection and response (EDR) tools can help identify suspicious behavior linked to malicious PDF malware. As this incident shows, even trusted software can harbor hidden dangers for months before a fix is released.

In conclusion, the PDF zero-day vulnerability patched by Adobe serves as a stark reminder of the evolving threat landscape. Staying vigilant and updating software promptly are the best defenses against such stealthy attacks. For more on securing your digital workspace, check out our guide on cybersecurity best practices for remote teams and learn how to secure PDF files against malware.

Continue Reading

CyberSecurity

Silent Security Risk: Google API Keys Quietly Grant Gemini Access on Android

Published

on

Silent Security Risk: Google API Keys Quietly Grant Gemini Access on Android

A newly uncovered flaw in Google’s API key system is putting Android applications at risk. According to a CloudSEK advisory published on April 8, the issue allows existing API keys to silently access Google’s Gemini AI platform without developer knowledge or user consent. This means that millions of Android users could be exposed to data breaches, unexpected costs, and service disruptions.

The vulnerability revolves around Google’s long-standing API key format, originally designed for public-facing services like Maps and Firebase. When the Gemini API is enabled in a Google Cloud project, existing keys automatically gain access to AI endpoints—no notification, no warning. This quiet shift creates a widespread risk that many developers are unaware of.

How the Google API Keys Gemini Access Flaw Works

CloudSEK’s research analyzed 10,000 Android apps using its BeVigil platform. The team identified 32 active keys across 22 applications, which collectively account for more than 500 million installs. In one confirmed case, researchers accessed user-uploaded audio files from an English-learning app via the Gemini Files API. The data included file metadata, timestamps, and accessible links—clear evidence that private content could be retrieved using exposed keys.

This behavior marks a departure from earlier Google guidance, which stated that such keys were safe to embed in client-side code. Developers who followed those recommendations may now be unknowingly exposing credentials linked to advanced AI systems. As a result, the Android app vulnerability is not just a theoretical risk—it’s a practical threat.

The Financial and Security Implications of API Key Exposure

The risks linked to this flaw are substantial. Attackers can access private files stored in Gemini, generate unauthorized API usage leading to financial losses, and disrupt services through quota exhaustion. Real-world incidents highlight the potential impact: one developer reported $15,400 in charges within hours of a compromised key being exploited. Another organization faced losses of $128,000, despite implementing security controls.

Furthermore, the mobile ecosystem amplifies the threat. App packages can be easily downloaded and analyzed to extract embedded keys. Many of these keys persist across multiple versions, increasing long-term exposure. This means that even if a developer updates their app, old keys may still be vulnerable.

What Developers and Users Should Do Now

CloudSEK’s advisory is clear: this is a structural flaw. ‘Google merged the concept of public keys with server-side AI secrets,’ the researchers wrote. ‘Enabling Gemini should have triggered a mandatory key restriction or forced the creation of a new, scoped key.’

Therefore, developers must take immediate action. First, audit all Google Cloud projects to identify which keys have Gemini API access. Second, rotate any exposed keys immediately. Third, restrict API access to only the services required. For users, the best defense is to keep apps updated and monitor for unusual activity.

Infosecurity Magazine has reached out to Google for comment on these findings, but has not received a response at the time of publication. In the meantime, the Android app vulnerability remains a pressing concern for the entire mobile ecosystem.

For more on AI security, read our article on Security Researchers Sound the Alarm on Vulnerabilities in AI-Generated Code. Additionally, learn about best practices for securing cloud APIs.

Image credit: Nwz / Shutterstock.com

Continue Reading

Trending