FeedExploreAsk AIAlertsSavedProfile

Categories

AICybersecurityInfrastructureDatabaseTech Updates

Tech news that matters.

FeedExploreAskAlertsSavedProfile
Back to feed
Cybersecurity·CriticalBreaking

Trusted WordPress Plugins Created Secret Admin Accounts

A security professional reviews a list of user accounts on a computer screen showing a WordPress dashboard.

TL;DR: A supply-chain attack compromised JavaScript files used by popular WordPress plugins like OptinMonster. The malicious code created hidden admin accounts on affected sites, giving attackers full control when an administrator was logged in.

By Neeraj Dhiman·3h ago·2 min read·updated 58m ago
Source

Key facts

Category
Cybersecurity
Impact
Critical
Published
3h ago
Source
The Hacker News

Full summary

A supply-chain attack on popular WordPress plugins created hidden admin accounts, giving attackers full control of affected sites when an admin logged in.

An attacker successfully compromised trusted third-party JavaScript files used by several popular WordPress plugins, including OptinMonster, PushEngage, and TrustPulse. This sophisticated supply-chain attack turned a legitimate marketing tool into a stealthy backdoor. The malicious code was designed to be patient and precise, activating only when a logged-in site administrator visited a page where the script was loaded. It did not trigger for ordinary website visitors, making it extremely difficult to detect through normal traffic monitoring or automated security scans. Once activated, the script automatically created a new, hidden administrator account on the WordPress site, giving the attacker the highest level of access and control. To ensure persistent access, the code also installed a hidden plugin, which acted as a permanent backdoor. This allowed the attacker to regain entry even if the initial vulnerability was fixed, enabling a complete and covert takeover of affected websites.

This incident is a critical reminder of the inherent risks associated with third-party dependencies in modern web development. When a site uses an external script, it implicitly trusts the security of that script's provider. If that provider is compromised, every website using their service becomes immediately vulnerable. For businesses running on WordPress, the impact of such a breach is severe. An attacker with full administrative privileges can steal sensitive user data, inject malware to infect visitors, add malicious SEO spam, or completely deface the site, causing significant reputational and financial damage. The stealthy nature of this particular attack means a compromise could go unnoticed for an extended period, allowing an attacker to establish a deep and persistent foothold within the system. This vulnerability affects any organization that uses these popular plugins to manage marketing and user engagement, putting their digital assets and customer trust at immediate risk.

Why it matters

This supply-chain attack highlights the hidden risks of using third-party scripts. A compromised dependency can grant attackers full control over a website, bypassing traditional security measures and leading to data theft or complete site defacement.

Business impact

A compromised website with a hidden admin can lead to severe business disruption, including data breaches of customer information, financial loss, and significant reputational damage. The cost of incident response and recovery can be substantial.

⚡ Action needed

Site administrators should immediately check for unauthorized admin accounts and suspicious plugins. Reviewing third-party script integrity is also recommended.

Action checklist

  1. 1Audit all administrator-level user accounts on your WordPress site.
  2. 2Remove any unfamiliar or unauthorized admin users immediately.
  3. 3Scan your site for unknown or suspicious plugins and themes.
  4. 4Force a password reset for all existing administrator accounts.
  5. 5Ensure all plugins, especially OptinMonster, PushEngage, and TrustPulse, are fully updated.
  6. 6Consider implementing a Content Security Policy (CSP) to restrict third-party scripts.

Tags

#security#vulnerability#malware#supply chain attack#wordpress

Related on Notifire

  • ResearchKubernetes security
  • ResearchCritical CVEs of 2026
  • ResearchSoftware supply-chain security
  • GlossaryCVE

✦ Notifire newsletter

Get more Cybersecurity intelligence

Join engineers getting Notifire’s verified tech briefings — short, sourced, and free. No spam, unsubscribe anytime.

The day's most important tech briefings. No spam, unsubscribe anytime.

Primary source: The Hacker News

Part of our research on

  • Critical CVEs of 2026 →

Tech intelligence for engineering teams

Short, verified briefings on AI, cybersecurity, infrastructure, and data — with the analysis and action steps that matter. Every briefing is sourced, fact-checked, and bylined to a named editor.

[email protected]Story tips & corrections welcomeHow we report →

The Notifire briefing

Verified tech intelligence in your inbox — AI, security, infra, and data.

The day's most important tech briefings. No spam, unsubscribe anytime.

Sections

  • AI
  • Cybersecurity
  • Infrastructure
  • Database
  • Tech Updates
  • Web3 & Chains

Newsroom

  • About Notifire
  • Editorial team
  • Editorial standards
  • Methodology
  • AI disclosure
  • Corrections

Resources

  • Explore
  • Research hubs
  • Comparisons
  • Tech glossary
  • FAQ
  • Alerts & watchlists

Follow

  • RSS feed
© 2026 NotifirePrivacyTermsCorrections
An independent, AI-assisted publication. Built at </Alpheric>
IntelligenceLive panel
Live

Top trending

Last 24h

    Popular tags

    Add to watchlist

    +OpenAI+Claude+PostgreSQL+Kubernetes+Cloudflare+AWS+CVE Critical

    Notifire score

    0–100 priority signal — combines impact, freshness, trending velocity, and source credibility.

  1. Atom feed
  2. LinkedIn
  3. X / Twitter
  4. Facebook
  5. Instagram
  6. YouTube