Under attack right now?

Emergency response050-1793-6936

Website tampering prevention: 10 things to do today to notice rewrites and restore the site

Types of website tampering and how to spot them, JPCERT/CC and police figures, priorities by site type, 10 things to do today, first steps and recovery cost.

Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated

Website tampering means a third party rewriting the contents of your site without permission. Some tampering swaps the top page for another screen. Some leaves the look unchanged and plants harmful links or instructions. It concerns companies that publish sites on WordPress, EC-CUBE or Shopify, and the agencies that run them. Tampering prevention has three parts, set up in order: fewer ways in for a rewrite, early notice when a rewrite happens, and a clean state you can return to.

This page is a hub. It helps a site owner see what kinds of rewrite exist, decide what to prepare first and decide who to call when damage occurs. If the site already looks wrong, or a search result shows words you do not recognize, read the emergency guide first.

What does tampering actually do to a site?

Many people picture a dramatic message on the screen. Quiet rewrites that the owner does not notice are also common. A large number of hidden links meant to manipulate search results may sit deep in a page. Instructions that steal card numbers may be planted only on the payment screen. Such rewrites leave the appearance unchanged, so the owner is slow to find them.

The JPCERT/CC cases later on this page show what rewrites were used for: hidden links to overseas online casinos, scripts that may steal card information, and a login page that served as a destination for voice phishing.

A rewrite is a result. If a site was rewritten, somebody had been able to write to it before that, through an entrance such as an admin login, an old plugin or a third-party script. Restoring the old content alone leaves the entrance in place.

What kinds of tampering are there, and how do you spot them?

Each kind of tampering shows up differently. The table lists the kinds a site owner should know, with the clue that tells you something is wrong.

Kind of tampering What happens Clue Read more
Replaced display The top page or other pages are rewritten with other content The look changes. Customers get in touch WordPress core vulnerabilities
Search result manipulation (SEO spam) Harmful links or text are shown only to search engines Words you do not recognize appear in the results for your company name WordPress plugin vulnerabilities
Unwanted redirects Under certain conditions, visitors are sent to another site Opening from a smartphone or a search result shows another screen HTTP header injection
Theft of payment data The purchase screen gets instructions that send what is typed to an outside party The look does not change. A card company's contact reveals it Card skimming
A fake login page A screen to steal credentials is placed inside the real site Pages or files you do not recognize appear File upload vulnerabilities
Rewrite of external parts An external script you load, such as advertising or analytics, is tampered with Your own files are intact, yet the display or behavior is odd Third-party script tampering
Hijacked DNS or subdomain Domain settings are changed and visitors are led to another server The site does not open, or a subdomain you do not recognize is live DNS misconfiguration

The kinds that are hard to see are search result manipulation and theft of payment data. To the owner who opens the site, both look normal.

So looking at the page is not enough. Once a month, check the search results for your company name, the display on a smartphone and the behavior of the payment screen. A mechanism in which a machine watches for file rewrites shortens the time until you notice.

We do not publish rewrite steps or examples of harmful code.

What do public statistics show?

A count of reports is a rough guide to how often something happens. The numbers below are taken from the publications named in each heading.

JPCERT/CC: 603 tampering reports in July to September 2026, about 3.3 times the previous quarter

JPCERT/CC, an organization that coordinates incident response in Japan, publishes the number of incident reports it receives every quarter. In its quarterly report for 1 July to 30 September 2026, published on 22 October 2026, reports of website tampering were 603. The previous quarter (April to June) had 181, so that is an increase of 233%.

By month, there were 116 in July, 194 in August and 293 in September, rising every month. The quarter before that (January to March) had 90, and April to June was 101% higher than that. Reports rose for two quarters in a row, to about 6.7 times in half a year (our calculation).

The 603 is about 7% of the 8,755 incidents in the same quarter (our calculation). Most of the rest were phishing sites, at 7,183.

The reports include cases that show how hard rewrites are to see.

  • On several legitimate sites in Japan, more than 5,000 lines of hidden HTML containing links to overseas online casinos and similar were embedded (July to September)
  • On several Japanese e-commerce sites built with EC-CUBE, JavaScript that runs instructions fetched from outside was embedded, along with a check for whether the visitor was on a purchase screen. The report notes the aim may have been to steal card information (July to September)
  • A rewrite that showed overseas online casino content only when a search engine's robot visited (April to June)
  • A legitimate site on which a suspicious login page and a remote control tool had been placed. It was used as the destination of voice phishing (April to June)

A person who simply opened the page would not see any of these rewrites.

Police, ministries: 13 recorded cases of website tampering or deletion

In the 2025 (Reiwa 7) publication under the Unauthorized Access Prohibition Act, website tampering or deletion was 13 among the acts carried out after unauthorized access. It was 9 the year before. Total recognized cases were 7,190, and most of those were unauthorized transfers and trades.

The 13 counts only what police recognized as unauthorized access. JPCERT/CC's report counts differently, so the two cannot be compared side by side. Both show that tampering is damage happening in Japan. The statistics on entrances are in preventing unauthorized access.

IPA: exploiting vulnerabilities is fourth, attacks on contractors second

In IPA's Top 10 Information Security Threats 2026 (29 January 2026), the threats to organizations rank as follows. First was damage from ransomware attacks. Second place went to attacks aimed at the supply chain or contractors. Third, new this year, was cyber risk from AI use. Fourth was attacks that exploit system vulnerabilities.

Entrances that lead to tampering overlap with two of these. A plugin hole that was not patched falls under fourth place. Access through an external part or a contractor's permissions falls under second. If an external part you load is rewritten, your site's display changes even though your own files are intact.

For EC-CUBE, IPA's alert of 25 December 2019 recorded about 140,000 leaked card records, as reported by the Ministry of Economy, Trade and Industry. On 14 October 2026 JVN published CVE-2026-103671, a hole in the official Amazon Pay plugin. The developer has confirmed exploitation in practice. Update payment-related parts without delay.

Want to see how your pages look from outside right now? The free URL check reads public information only and costs JPY 0.

What should you do first, by type of site?

Start with the steps that fit your site.

A company-profile site left to an outside agency

Nobody is looking at the site, and it can be rewritten quietly again and again. Profile sites change rarely, so nobody notices a change.

Open the search results for your company name and look at the site on a smartphone. Then ask who updates the core and plugins, and when, in the maintenance contract. If the answer is vague, put backups and tamper detection in first.

A site with contact forms or member pages

More screens carry typed information, so a rewrite does more harm. If the destination of a form is rewritten, what your customers type flows outside.

Update the plugins that supply forms first. Add a mechanism that detects file rewrites, and decide who receives its alerts. Check that the alerts do not go to the address of someone who has left.

A site with e-commerce or payment screens

When card information is stolen through the payment screen, work multiplies at once: harm to customers, reports to card companies and a stopped site.

Do not put off updates to payment-related plugins. List the external scripts the payment screen loads and remove those you do not need. Then build into operations an assessment after each large change and a way to detect rewrites of the payment screen.

10 things to do today

These 10 come from our fix menu. They shrink the ways in, help you notice a rewrite and give you a way back. The examples use WordPress, and other CMSs work on the same principle. Each item tells you whether you can do it from the admin screen or should ask a specialist.

  1. Update the core, themes and plugins, and delete parts you do not use. Holes in old parts can be an entrance for a rewrite. Delete the ones that are only deactivated.
  2. Tidy administrator accounts and passwords. Delete administrators nobody needs and replace weak passwords. Fewer people who can write means fewer entrances for tampering.
  3. Turn on two-factor authentication. Even if a password leaks, nobody can enter the admin screen without the confirmation on a phone.
  4. Limit where the admin screen can be reached from. Allow it only from fixed places. Because server settings are involved, leave it to a specialist if you are unsure.
  5. Keep key files out of reach and review permissions. Put configuration files where they cannot be read from outside, and narrow what can be written to the minimum.
  6. Close entrances you do not use. Close XML-RPC and other communication channels that nothing depends on.
  7. Detect file tampering. A machine watches the files and tells you when one is rewritten. It is a strong way to notice tampering that leaves the look unchanged.
  8. Back up every day, and prove a restore works. A backup on its own is not enough. Make it possible to tell which point in time was clean, and try a restore once.
  9. Put a WAF in front of the site. A WAF screens traffic at the entrance. It filters dangerous requests before they arrive, and it can be a temporary shield while a fix is awaited (WAF).
  10. Set up encryption (SSL) and security headers. Traffic is encrypted, and settings that make the browser block harmful loading are switched on.

Start with items 1 to 3. From item 4 onward, a wrong setting can lock you out of your own site, so take a backup first. Even a finished list gives no promise that your site will never be rewritten. It lowers the chance, and helps you notice and restore sooner when it happens.

If these jobs will not fit into your week, tell us about your site. We will check with you which of the 10 are not yet in place.

What should you do first when you notice tampering?

When the display looks wrong, the urge is to delete files in a hurry. Evidence comes first. What was rewritten, when and through which entrance can be known only from the files and logs that remain.

Take these steps in order.

  1. Save the current files and logs, as they are, to another place.
  2. Change the passwords for the admin screen, the server and the database.
  3. Contact us through the emergency guide. If the payment screen is in doubt, discuss stopping payments at the same time.

We do not recommend restoring from a backup without closing the entrance. The same hole may be used to rewrite the site again.

What should you hand to a specialist?

Decide who does a job by asking whether a mistake can be undone and whether the job needs skill to examine the inside of the site.

  • Investigation and recovery after damage. Recovery from tampering or malware damage is from JPY 29,800 (excl. tax), and covers finding the cause, removing harmful code and setting up recurrence prevention. If you want us to move today, a same-day start adds JPY 20,000 (excl. tax). The amount moves with the size of the site, the number of files and how far the damage spread.
  • Assessment of the hole that served as the entrance. After recovery, we check whether the same kind of hole exists elsewhere. A WordPress/CMS site assessment is from JPY 49,800 (excl. tax, up to 30 pages), and one re-assessment after fixes is free. Screens behind login and the count of paid plugins affect the amount.
  • Hardening in one go. The WordPress security hardening pack is from JPY 49,800 (excl. tax). It covers updates, permission review, detection and a WAF from the fix menu.
  • Assessment of payment screens. Web application assessment Lite is from JPY 98,000 (excl. tax, up to 10 screens). It checks the screens up to purchase.
  • Continuous watch. Watching files for rewrites every day stops the moment a person forgets. Guard, our AI monitoring for WordPress, includes tamper detection in Lite at JPY 5,000 per month (excl. tax). Maintenance Lite, which also handles updates and tamper monitoring, is JPY 9,800 per month (excl. tax).

Our work is to investigate and recover after damage, to fix the holes we find and to watch afterwards. A PDF of changes comes before delivery, and you check the live screens yourself. The first month after delivery is supported at no charge.

No one can promise that a site will never be rewritten, since methods keep changing. An assessment confirms known holes only and does not secure the future.

Which pages cover the individual holes?

Holes that lead to a rewrite have their own pages. They give the mechanism, a check and a fix.

CMS and e-commerce parts

Web applications

Domains, backups and AI

The other hubs are hacking prevention, preventing unauthorized access and ransomware prevention.

How can the free URL check help you decide?

Decide what to prepare after you see where you stand. The free URL check starts from the address of your site. It covers only information visible to anyone: certificate expiry, security headers, the external parts your pages load, versions of public components with their known holes, and email authentication settings. No login is attempted and no attack is sent. The cost is JPY 0.

Should the result raise a concern, we sign an NDA, collect your assessment consent form and perform the free assessment, a quick tool scan plus a person's review. You read the issue report before choosing whether to order fixes.

Frequently asked questions

How can I tell whether my website has been tampered with?

Search for your company name and see whether the title or description contains words you do not recognize. Also check how the site looks on a smartphone, how it looks when opened from a search result, and whether the payment screen looks as usual. Harmful code can be added without any change in appearance, so use a mechanism that detects file rewrites as well.

What should I do first if my site has been tampered with?

Before you delete or overwrite any file, save the current state and the logs. Next, change your admin and server passwords and reach us through the emergency guide. If you restore the site without closing the entrance, the same hole may be used to rewrite it again.

Is a backup enough for tampering prevention?

No. A backup is preparation for restoring and it does not close the entrance. A backup taken before you noticed the tampering may have saved the harmful code along with everything else. Before you restore, you need to confirm which point in time was clean.

How much does recovery from tampering cost?

Recovery from tampering or malware damage is from JPY 29,800 (excl. tax) and covers finding the cause, removing harmful code and setting up recurrence prevention. A same-day start adds JPY 20,000 (excl. tax). The amount moves with the size of the site, the number of files and how far the damage spread. A formal quotation follows once we have checked the situation.

Next step

Today's work has three parts. Start on items 1 to 3 of the list above. Check the search results for your company name and your site on a smartphone. Then run the free URL check.

To decide priorities and what to outsource, contact us. If the display already looks wrong, or the payment screen is in doubt, use the emergency guide first.

Written by Mio Kanzaki (AI security analyst). Supervised by 千葉圭介. Updated 19 November 2026.

Frequently asked questions

How can I tell whether my website has been tampered with?

Search for your company name and see whether the title or description contains words you do not recognize. Also check how the site looks on a smartphone, how it looks when opened from a search result, and whether the payment screen looks as usual. Harmful code can be added without any change in appearance, so use a mechanism that detects file rewrites as well.

What should I do first if my site has been tampered with?

Before you delete or overwrite any file, save the current state and the logs. Next, change your admin and server passwords and reach us through the emergency guide. If you restore the site without closing the entrance, the same hole may be used to rewrite it again.

Is a backup enough for tampering prevention?

No. A backup is preparation for restoring and it does not close the entrance. A backup taken before you noticed the tampering may have saved the harmful code along with everything else. Before you restore, you need to confirm which point in time was clean.

How much does recovery from tampering cost?

Recovery from tampering or malware damage is from JPY 29,800 (excl. tax) and covers finding the cause, removing harmful code and setting up recurrence prevention. A same-day start adds JPY 20,000 (excl. tax). The amount moves with the size of the site, the number of files and how far the damage spread. A formal quotation follows once we have checked the situation.

See what an attacker can see, today

The free URL check returns a grade in under a minute. For costs and next steps, book a free consultation.