Wordfence recorded a 3.25-fold rise in Taiwanese websites with blocked malicious file-upload requests from October 26 to November 13, 2026. Its November 19 report traced much of that activity to one IP address, 45.38.60.254. For site owners following WordPress attacks on Taiwan sites, the useful detail is the shape of the scan: it focused heavily on .tw domains and targeted known vulnerabilities.
The report draws on Wordfence firewall logs, not a count of every website in Taiwan. It does not identify a successful compromise. Here is what the data establishes, what it leaves open, and what WordPress site owners can check in response.
In brief: Wordfence says one scanner, 45.38.60.254, drove much of the late-October rise in blocked requests against .tw websites. Its firewall blocked or logged more than 246,000 requests from the address. Wordfence says the requests targeted known vulnerabilities and its generic rules blocked them; it found no web shell or backdoor in the uploads it examined.
What WordPress attacks on Taiwan sites looked like
In its November 19 analysis, Wordfence compared daily counts of websites where its firewall blocked at least one request. The review covered six Asian country-code domains from September 1 through November 15: Taiwan (.tw), Japan (.jp), South Korea (.kr), Hong Kong (.hk), Singapore (.sg), and China (.cn).
Only .tw showed a significant change during the period, according to the report. Wordfence deliberately counted affected websites rather than raw requests for its regional comparison. A single website can receive a flood of requests; counting sites instead helps show whether activity is spreading across a wider set of targets.
The increase was concentrated in two rule categories
From October 26 to November 13, an average of 426 .tw websites per day had requests blocked under Wordfence’s Malicious File Upload rule. The average for the previous eight weeks was 131 per day. For SQL injection, the daily average rose from 216 .tw websites to 599 over the same comparison.
Wordfence calculated that attacked .tw websites increased 3.25 times for malicious file uploads and 2.77 times for SQL injection. The data also showed a sevenfold increase in the Malicious File Upload (PHP) category on .tw, a larger rise than on the other domains examined. On November 14 and 15, the SQL injection count fell to 102 and 97 sites.
One IP address drove much of the scan
Wordfence’s records show the address 45.38.60.254 first appeared on October 26. Between then and November 13, it reached between 568 and 863 firewall-protected websites each day. From November 14, the number dropped to 15 or fewer per day.
For the general malicious file-upload rule, Wordfence counted 5,541 attacked .tw websites across November 1 to 13. It attributed 3,732 of those counts, or 67%, to the address. The IP triggered the PHP upload rule on 403 .tw websites and 122 websites under other domains. Wordfence says it did not see that rule triggered on .jp, .kr, .hk, .sg, or .cn sites by this address.
That concentration matters when interpreting the headline. Wordfence described the activity as likely mapping of Taiwanese sites, including WordPress sites, for vulnerable targets. Its findings point to one scanner doing much of the work, rather than evidence that attacks rose evenly across the region.
What the findings do and do not show
The report lists blocked requests under rules for SQL injection, directory traversal, malicious file uploads, local file inclusion, and cross-site scripting. It says requests blocked by the two malicious file-upload rules targeted previously disclosed vulnerabilities in WordPress plugins and other web software. The CVE identifiers in the payloads dated from 2017 to 2024.
Wordfence says the upload samples it inspected contained a short PHP snippet that printed a hash to test whether an upload succeeded. It did not find a web shell or backdoor in those files. The firewall blocked or logged the requests, and Wordfence says generic rules handled the activity without a vulnerability-specific rule.
Those details set a boundary around the report. It documents probing and blocked attempts, not confirmed intrusions or a newly disclosed plugin flaw. The data also comes from websites protected by Wordfence, so it should not be read as a census of all Taiwanese websites or all WordPress attacks.
What WordPress site owners should check
Wordfence’s report does not name a particular plugin that site owners should remove. It does show attempts against known vulnerabilities in older software. The practical response is routine maintenance, not a special fix for this IP: check that WordPress, plugins, and themes are updated, and remove components the site no longer uses.
Site owners who review firewall or server logs can look for repeated requests against upload paths and other vulnerable endpoints. A blocked request is evidence that a rule intervened, not proof that an attacker got in. If logs show successful uploads or unexpected files, investigate those files and the affected accounts rather than relying on the request count alone.
For sites in Taiwan, the sharpest rise in this report had already eased by November 14. That does not establish that scanning has stopped or that the same source will not return. Keep software current and check the site’s own logs for activity that its security controls did not block.
FAQ
Did Wordfence confirm that Taiwanese WordPress sites were compromised?
No. The report describes requests blocked or logged by the Wordfence Firewall. Wordfence says the upload attempts it examined did not contain a web shell or backdoor, and it does not report confirmed compromises.
What caused the rise in attacks on .tw websites?
Wordfence traced much of the increase to IP address 45.38.60.254, which began appearing in its data on October 26, 2026. The company said the pattern suggested the scanner was mapping Taiwanese websites for known vulnerabilities.
What should WordPress site owners do?
Keep WordPress core, plugins, and themes updated, and remove software the site does not use. Review security logs for signs of successful activity as well as blocked requests, especially if the site received repeated upload attempts.
Next step: Check your WordPress update screen and review recent security logs for upload attempts that were not blocked.