Looking for WordPress answers? WordPress Hub Magazine website is designed to be a central hub for discovering all WordPress knowledge. Curated, aggregated and custom content for people who use WordPress.
On this blog we write a lot about different vulnerabilities that could lead to site compromise. In our Learning Center we go deep on a myriad of important topics related to WordPress security. Our handy checklist, for example, includes 42 items you really should be paying attention to. But surely not all 42 items are equally important, right? In today’s post we dive into some very interesting data we gathered a couple of weeks ago in a survey, letting the facts tell us what matters most.
This past weekend we registered a spike in WordPress infections where hackers injected encrypted code at the end of all legitimate .js files.
The distinguishing features of this malware are:
32 hex digit comments at the beginning and end of the malicious code. E.g. /*e8def60c62ec31519121bfdb43fa078f*/ This comment is unique on every infected site. Most likely an MD5 hash based on the domain name.
The first comment is immediately followed by ;window[“\x64\x6f…. and a long array of string constants in their hexadecimal representation.
In the midst of a malware emergency or want to ensure you never have to deal with one? Columnist Glenn Gabe provides recommendations based on his experience helping clients with security situations.
Security warnings in Google Search Console (GSC) can be scary. Really scary. Whether your site was flagged for being hacked, serving malware, unwanted software or worse, security warnings in GSC can cause serious problems for your organization.