Under attack right now?

Emergency response050-1793-6936

How to prevent hacking: what to do today and what to hand to a specialist

Attack types, what Japan's police and IPA statistics show, priorities by company size, 10 things to do today, and what to hand to specialists.

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

Hacking prevention means making it hard for an outsider to get into your website or systems, and easy for you to recover if one does. The outsider might steal information, rewrite pages or stop your service. It concerns companies that run sites on WordPress, EC-CUBE or Shopify, companies with their own systems, and the agencies that look after those sites. Three jobs come first: clear out parts that are no longer updated, strengthen the login, and keep a backup you have proven you can restore.

This page is a hub. It lets a site owner see what is happening, decide what to do first and decide where to bring in a specialist. Pages on individual holes are listed near the end. If damage is happening now, read the emergency guide first.

What does a hacker actually do to a site?

Hacking is an outsider getting into your website or systems without permission. The statistics later on this page show which doors were used in recorded cases: VPN devices, remote desktop and holes that had not been fixed.

After entry, the intruder usually does one or more of four things. They steal information. They rewrite pages, which is tampering. They use your server as a stepping stone to attack others. They hold your data hostage, which is ransomware. The goal decides which one happens, and a single break-in can lead to several at once.

For that reason, think in three layers: reduce the ways in, notice quickly when someone gets in, and be able to restore. If you rely on one layer and it fails, nothing is left behind it. The fix menu we offer is built around the same three layers.

Which attacks are there, and where do they enter?

"Hacking" covers attacks of different kinds. Once you know where each one enters, the order of repair follows. The table sorts the kinds that a site owner should know by route of entry.

Kind of attack What happens Where it enters Read more
Unauthorized login (guessing, reused passwords) Someone logs in to the admin area as a legitimate user Login screens of admin areas, VPNs and email Preventing unauthorized access
Abuse of a known vulnerability A hole with a published fix is used to control the system remotely WordPress core, plugins and server software that were not updated Unpatched software
Abuse of VPN devices and remote connections The attacker gets inside the company network VPN appliances, remote desktop Preventing unauthorized access
Attacks on flaws in a web application Database contents are read, or harmful instructions are planted in a page Contact forms, search boxes, member pages SQL injection, XSS
Attacks on configuration mistakes Files or admin screens that should be private become visible from outside Server settings, open ports, default settings left as they were Security misconfiguration
Attacks through parts and business partners The attacker comes in through parts you did not write or a contractor External libraries, plugins, access given to a maintenance company Preventing supply chain attacks
Impersonation to steal credentials A convincing message gets you to type your own ID and password Email, phone calls (voice phishing), fake sites Preventing phishing
Attacks on AI features A chatbot or similar tool is made to follow harmful instructions Screens or automated processes that embed generative AI Prompt injection

Two rows come up again and again in later sections: the known hole that was left unfixed, and the weak login. Common doors like these are worth closing before you worry about a skilled attacker.

We do not publish the steps or strings an attacker would use. A reader who wants to defend needs only the entry points and the countermeasures.

What do public statistics show?

Figures help you judge your own situation. Every number below was checked against its original publication, and the source and year are named with it.

National Police Agency: most victims are small and medium-sized companies, and most entries came through VPN devices

The National Police Agency counted 226 ransomware cases reported to police in 2025 (Reiwa 7). Ransomware is an attack that encrypts or steals data and demands money. By size, 64 cases were at large companies and 143 at small and medium-sized companies, so small and medium-sized companies made up more than 60% (2026 White Paper on Police).

The same report shows how attackers got in. In a survey of victim companies with 92 valid answers, 61 (66.3%) were entered through a VPN device and 19 (20.7%) through remote desktop. The doors that connect from outside to the company network were the doors the attackers used.

Another figure concerns double extortion, where criminals threaten to publish stolen data. Among 153 cases in which police could confirm the method of a ransom demand, double extortion accounted for 136 (88.9%). A backup can bring a service back, but it cannot bring stolen data back. Preparing to restore and preparing to keep intruders out are separate jobs.

Unauthorized internet banking transfers are also in the White Paper. In 2025 there were 4,747 cases with about JPY 10.397 billion in losses, the highest amount on record. The White Paper names a sharp rise in corporate account losses from voice phishing, where a caller poses as a bank, as one factor.

IPA: exploiting vulnerabilities ranks fourth among threats to organizations

The 2026 edition of IPA's Top 10 Information Security Threats came out on 29 January 2026. For organizations, first place went to damage from ransomware attacks. Second was attacks aimed at the supply chain or contractors. Third was cyber risk from the use of AI, which entered the list for the first time. Fourth was attacks that exploit system vulnerabilities.

The first, second and fourth entries bear directly on hacking prevention. They overlap in where they enter: parts that were not updated, weak authentication and access handed to business partners. Look at that common ground rather than at the change in rank.

The number of holes keeps growing

Patchstack's State of WordPress Security in 2026 counts 11,334 new vulnerabilities in the WordPress ecosystem in 2025. The count is up 42% on the year before, and plugins were the source of 91% of the new holes. As of 19 November 2026, W3Techs reports that WordPress is used by 38.5% of all websites and by 57.4% of the websites whose CMS it can identify. Because it is so widely used, a single hole can affect many sites.

OWASP's Top 10:2025 sorts the web application risks in order. First is broken access control, second is security misconfiguration and third is software supply chain failures.

After reading the statistics, you may want to see how your own site looks. The free URL check reads only what anyone can see from outside, and it costs JPY 0.

What should you do first, by company size?

You do not need to do everything at once. Take the steps that matter most for the shape of your company.

A company of a few people up to about 20, with site updates outsourced

With few people touching the site, start by checking whether anyone is updating it. Work in this order: name who updates, review administrator accounts, turn on two-factor authentication and test a restore.

If an agency does your updates, ask in the contract or in a maintenance email who updates the core and the plugins, and when. If the answer is vague, treat the site as unattended until you confirm otherwise.

A company of a few dozen with an internal network and several sites

You now have places to protect beyond the website. In the police data, VPN devices were the entry point in two-thirds of the surveyed cases, so VPN appliances and remote desktop are the first things to inspect.

Update the firmware, which is the software inside the device. Stop exposing what does not need to be public, and add two-factor authentication to logins. Then write a list of the devices that face the internet.

A company with e-commerce, a member site or its own system

Sites that hold card data or personal data can suffer larger damage. In EC-CUBE, the Ministry of Economy, Trade and Industry reported in 2019 that about 140,000 card records had leaked (IPA alert of 25 December 2019). JVN published a vulnerability in the official Amazon Pay plugin on 14 October 2026 (CVE-2026-103671), and the developer has confirmed that it was exploited in practice. Update payment plugins without delay.

At this level, what you can protect yourself has limits. Build three habits into operations: an assessment before launch and after each large change, a way to detect tampering on payment screens, and an emergency contact decided in advance.

10 things to do today

These 10 come from our fix menu. They are the ones a site owner gains most by starting first. The list assumes WordPress, and the thinking is the same for other CMSs. Some can be done from the admin screen. Others are safer in a specialist's hands, and those say so.

  1. Update, and delete parts you do not use. Bring the core, themes and plugins up to date. Delete anything that is only deactivated. Old parts left in place are easy targets, and the "Updates" page in the admin screen is enough to check.
  2. Tidy administrator accounts and passwords. Remove administrators who are no longer needed and end weak or reused passwords. Check for people who left and for accounts of a previous agency.
  3. Turn on two-factor authentication. Even if a password leaks, nobody can log in without the confirmation on a phone. An authenticator app is a simple way (two-factor authentication).
  4. Limit login attempts. Stop connections that fail many times in a short period. This blunts guessing attacks that try passwords one after another.
  5. Change the login URL and restrict where the admin area can be opened from. The admin screen becomes harder to find and opens only from fixed places. This touches server settings, so hand it over if you are unsure.
  6. Close doors you do not use. Shut off XML-RPC and other channels you never use. Fix the situation where login names can be seen from outside.
  7. Take a daily backup and test a restore. Having a backup is not enough. Restore it once and learn the steps and the time it takes.
  8. Detect file tampering. Harmful code is sometimes added while the page looks the same. Set up something that notices when files are rewritten.
  9. Set up encryption (SSL) and security headers. Traffic is encrypted, and the browser's own defenses are switched on.
  10. Set up a WAF, a mechanism that stops bad traffic before it reaches the site. It can also serve as a stopgap until a fix is released (WAF).

Start with items 1 to 4. From item 5 onward, a wrong setting can lock you out of your own site, so take a backup first. Finishing all 10 does not guarantee that no damage will occur. The work lowers the chance of damage and makes it smaller when it happens.

If you cannot find the time yourself, talk to us about your situation. We will go through which of the 10 are still open with you.

What should you hand to a specialist?

There is a clear line between what you can do yourself and what is safer to hand over. Two questions draw the line: can a mistake be undone, and does the job need skill to examine the inside of the site?

We recommend a specialist for these:

  • Vulnerability assessment. From outside, you cannot tell whether your site really has holes. Our WordPress/CMS site assessment is from JPY 49,800 (excl. tax, up to 30 pages), and one re-assessment after the fixes is free. The price rises with screens behind login and the number of paid plugins.
  • Investigation and recovery when you suspect damage. Before anyone touches files, steps must be taken so that evidence is not lost. Recovery from tampering or malware damage is from JPY 29,800 (excl. tax), and covers finding the cause and setting up recurrence prevention. A same-day start adds JPY 20,000 (excl. tax).
  • Review of server and network device settings. Tidying VPN appliances and open ports can stop business if it goes wrong.
  • Assessment of systems where a failure does great harm, such as payment, membership and APIs. Web application assessment Lite is from JPY 98,000 (excl. tax, up to 10 screens).
  • Continuous watch. Updates, monitoring and backups that must run every month stop the moment a person forgets. Maintenance Lite is JPY 9,800 per month (excl. tax). Guard Lite, our AI monitoring for WordPress, is JPY 5,000 per month (excl. tax).

We confirm and fix the holes an assessment finds, investigate and recover after damage, and keep watch afterwards. We report what we changed in a PDF before delivery, and you check the actual screens before we deliver. Support for the first month after delivery is free.

We do not promise that an attack can be prevented. Attack methods keep changing. An assessment confirms that the holes known today are not present, and it does not guarantee future safety.

Which pages cover the individual holes?

These are the pages on holes related to hacking prevention. Each explains how the hole works, how to check for it and how to fix it, for operators and for developers.

Web applications and apps

Servers, CMS and parts

Generative AI and LLMs

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

How can the free URL check help you decide?

You need to know where you stand before choosing what to fix. The free URL check works when you enter the address of your site. It reads only what anyone can see from outside, such as the expiry of the encryption certificate, security headers, the versions of public components and known holes in them, and email authentication settings. It does not try to log in and does not send attacks. It costs JPY 0.

If something in the result worries you, we sign a non-disclosure agreement (NDA), take your assessment consent form, and run the free assessment, a quick check by tools and a person. You see the issue report before deciding whether to order fixes. A formal quotation follows the free assessment.

Frequently asked questions

Is a small company's website a target for hackers?

Yes. Small and medium-sized companies are hit. The National Police Agency reports that 143 of the 226 ransomware cases reported to police in 2025 were at small and medium-sized companies.

Where should I start with hacking prevention?

Start by updating the WordPress core, themes and plugins that have fallen behind, and by deleting the ones you do not use. Next, tidy up administrator accounts, turn on two-factor authentication, and check that a backup can really be restored.

If I install a security plugin, do I still need a specialist?

A plugin reduces bad traffic, but it cannot fix the holes in how your site is built. Decide who answers when it raises a warning, and combine it with a regular assessment.

How much does hacking prevention cost?

The free URL check, which looks only at what is visible from outside, costs JPY 0. A WordPress/CMS site assessment is from JPY 49,800 (excl. tax, up to 30 pages). The amount moves with page count, screens behind login and paid plugins. A formal quotation follows the free assessment.

Next step

Today's work has two parts. Start on items 1 to 4 of the list above, and at the same time look at your own site with the free URL check.

To talk through priorities and what to hand over, contact us. If you already suspect damage, use the emergency guide first.

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

Frequently asked questions

Is a small company's website a target for hackers?

Yes. Small and medium-sized companies are hit. The National Police Agency reports that 143 of the 226 ransomware cases reported to police in 2025 were at small and medium-sized companies.

Where should I start with hacking prevention?

Start by updating the WordPress core, themes and plugins that have fallen behind, and by deleting the ones you do not use. Next, tidy up administrator accounts, turn on two-factor authentication, and check that a backup can really be restored.

If I install a security plugin, do I still need a specialist?

A plugin reduces bad traffic, but it cannot fix the holes in how your site is built. Decide who answers when it raises a warning, and combine it with a regular assessment.

How much does hacking prevention cost?

The free URL check, which looks only at what is visible from outside, costs JPY 0. A WordPress/CMS site assessment is from JPY 49,800 (excl. tax, up to 30 pages). The amount moves with page count, screens behind login and paid plugins. A formal quotation follows the free assessment.

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.