What actually happened to websites. With sources, in one place.
13,687 a day
Suspicious accesses probing for weaknesses reaching police sensors (per address)
1,748
Vulnerabilities confirmed as exploited in real attacks (US CISA KEV)
58
Incidents in this record, all with sources
Updated:
57 incidents
1 for reference
5 figures
CYBER ATTACKERS
What cyber attackers do, in government figures.
Before choosing a single site, cyber attackers sweep many sites by machine, looking for vulnerable versions and missing settings. This is not about particular organizations: every public site is part of the sweep.
Organized cyber attackersAfter ransom and more
Automated sweeps24 hours a day, 365 days a year
Probe sites nationwideCollect version numbers and missing settings
A weakness is foundOld versions, missing settings
13,687 a day
Police sensors receive 13,687 suspicious accesses probing for weaknesses per address per day, most of them from overseas.
NICT observed about 2.5 million attack-related packets per address in a year, which works out to about one every 13 seconds. The National Police Agency notes that public devices and services are operated on the premise that third parties constantly probe them.
Ransomware (attacks that hold data hostage for payment) reports hit a record 123 for a half-year since statistics began. Cyber attackers break in by exploiting unpatched vulnerabilities and leaked credentials.
The US CISA (Cybersecurity and Infrastructure Security Agency) publishes a catalog of vulnerabilities confirmed as exploited in real attacks (KEV). As of 2026-10-16, it lists 1,748 entries. US federal agencies are required to fix listed weaknesses by set deadlines.
Figures are summarized by KnownFor from each agency’s published material and are not quoted verbatim. Please see the sources for details.
INCIDENTS
Incidents
“Related findings” are the KnownFor scan findings that show, within what is visible from outside, the same kind of weakness as the cause or harm in the incident. They do not mean KnownFor detected the incident itself.
Two PHP vulnerabilities (PHP2Shell) and service suspensions in Japan (Oct 2026)
Source: The PHP Foundation (Oct 21, 2026) and 5 more · Sources checked:
1Two PHP flaws that could let outsiders run programs
2PHP 5.4 through 8.5.11 affected
3Many services in Japan temporarily stopped
4Update to a fixed version (none for 8.1 and earlier)
Who was affected, and how
Operators of sites that run on PHP: the server’s PHP needs to be on a fixed version (8.5.12, 8.4.27, 8.3.36 or 8.2.35). Updating WordPress or plugins alone does not fix it. Service users: many services in Japan were temporarily stopped and could not be used for a time.
What happened
Two vulnerabilities were found in PHP, the programming language that runs many websites, that could let an unauthenticated third party run programs on the server from outside, and the PHP development team released fixed versions on October 21, 2026 (around 23:00 Japan time). The vulnerabilities are CVE-2026-109618 and CVE-2026-109619 (severity 9.2 in CVSS v4.0) and affect PHP 5.4 through 8.5.11. The fixed versions are 8.5.12, 8.4.27, 8.3.36 and 8.2.35; the development team does not release fixes for 8.1 and earlier, which are out of support. Because information got out before the announcement, IPA and Japan’s National Cybersecurity Office called for advance preparation, and the Prime Minister said that temporarily stopping a website is also an effective option when it cannot be fixed. In Japan, many services, including online shops, a childcare-facility service, video and games, were temporarily stopped around the time of the fix. Cloudflare said it had seen early attacks and added rules to block known attack methods.
This is a record of the vulnerabilities and the response to them, not an announcement of damage. KnownFor’s scan reads only what is visible from outside, so for sites that hide the PHP version number it cannot tell whether the fixed version is in use (please check with your hosting company or web vendor).
Japan, South KoreaBusiness / schoolData leak
Intrusions using an AI penetration-testing tool (Oct 2026)
Source: GMO Cybersecurity by Ierae (Oct 19, 2026) and 3 more · Sources checked:
1A tool where AI investigates and tests on its own
2About 20 Japanese companies as targets
38 of them disclosed data leaks
4Attack-server details shared with law enforcement
~20 companies
Japanese companies targeted by the one attack server examined
Who was affected, and how
Targeted companies: 8 of them disclosed data leaks in September–October (the names were not announced). The investigating firm: shared the attack-server information with law enforcement.
What happened
GMO Cybersecurity by Ierae announced that ARTEX, a penetration-testing tool in which AI investigates and tests on its own, was used on attack servers behind a series of intrusions. The one server examined had about 20 Japanese companies as targets (9 of them in the same industry), and 6 more similar attack servers using AI were found. Of the targets, 8 companies disclosed data leaks in September–October (being a target does not mean every company was breached). CrowdStrike reported that the same tool was used in attacks on South Korean financial institutions. The tool had been public; publication has since stopped.
The entry weakness has not been disclosed. In a separate article (Oct 15), GMO notes that cyber attackers use AI to look for weaknesses in end-of-support products and in versions not listed in the vulnerability catalog (CVE). It is shown here as the same kind of finding.
Related findings in a KnownFor scan
sec-eolSoftware that is no longer supported is visibleHow to stop it: Apply updates to move to a supported version.
sec-version-exposedSoftware version numbers are visible from outsideHow to stop it: Stop showing version numbers to the outside.
sec-old-libraryAn outdated JavaScript libraryHow to stop it: Replace the library with a current version.
Municipal disaster-alert email service, Japan (Oct 2026)
Source: Arcadia Inc. notice on unauthorized access (from Oct 13, 2026) and 3 more · Sources checked:
1Unauthorized access to a contractor’s messaging service
2About 3.14 million email addresses may have leaked
3Suspicious email reaches subscribers (Yokosuka)
4Municipalities stop services and issue warnings
~3.14 million
Email addresses that may have leaked (operator’s estimate)
Who was affected, and how
Residents and staff who registered for disaster-alert email and similar services: their email addresses and other details may have leaked, and in Yokosuka subscribers were already receiving suspicious email. Municipalities: stopped the services, sent information through official websites, social media and outdoor loudspeakers, and reported to the Personal Information Protection Commission (Yokosuka).
What happened
Arcadia Inc. announced that SpeeCAN RAIDEN, a bulk-messaging service used by municipalities across Japan for disaster-alert email and similar services, was accessed by a third party without authorization. The data that may have leaked is estimated at about 3,136,000 email addresses, about 105,000 phone numbers and about 15,000 fax numbers. Yokosuka City said the email addresses of 47,065 disaster-alert subscribers and others may have leaked and that subscribers were already receiving suspicious email, and it stopped four services. The same company also announced a possible leak of users’ names, dates of birth, addresses and more from its emergency 119 reporting service (NET119).
This was an incident at a contractor’s service, not the municipalities’ own websites. The method of intrusion has not been disclosed, and no link to the attack AI agent (ARTEX) has been announced.
Applicants: their names, contact details and more could be seen by other applicants. The organization: explained and apologized to all 40 people by email and phone, and told the contractor to set up double-checks for work involving personal data.
What happened
On an event application form for a program the city outsourced, the contractor set the viewing settings incorrectly, so applicants could see what other applicants had entered. The names, school grades, phone and fax numbers, email addresses and reasons for applying of 40 people were affected. An applicant reported it on October 14, and the contractor fixed the setting the same day.
The cause was not encryption (https), but it is an example of form input being seen by others.
Related findings in a KnownFor scan
sec-form-insecureForms that send data without protectionHow to stop it: Make the form send to an https address.
Source: ScanNetSecurity (Sep 30, 2026) and 1 more · Sources checked:
Who was affected, and how
Residents and users: the digital archive service became unavailable. The organization: said it would decide on fixing the vulnerability, preventing a repeat and reopening based on the investigation. It states no personal information was stored on the site and no infection of users’ devices has been confirmed.
What happened
On July 14, the city’s digital archive site “Dejimachi” was accessed through a system vulnerability, and some pages were altered into pages leading to online casino sites. It was found on August 28 after an outside report. The city disconnected the system from the network, stopped the service and is investigating.
Related findings in a KnownFor scan
sec-eolSoftware that is no longer supported is visibleHow to stop it: Apply updates to move to a supported version.
sec-old-libraryAn outdated JavaScript libraryHow to stop it: Replace the library with a current version.
United Kingdom (Scotland)Government / public bodySent to a fake site
Scottish Borders Council, UK (2026)
Source: NEXT.io (Sep 3, 2026) · Sources checked:
16
of 69 links that led to gambling sites
Who was affected, and how
People looking for their community council via the council site: were sent to gambling sites. The council: removed all affected links.
What happened
Of the 69 links to local community councils on the Scottish Borders Council website, 16 led to offshore online gambling sites. Fifteen of the 16 had been hosted on a third-party directory that became unresponsive about eight years earlier, and the old links had stayed on the site. After a BBC Scotland report, the council removed all affected links.
Related findings in a KnownFor scan
ai-gov-unofficial-urlAI gives an unofficial address
ai-gov-dead-linkOfficial pages AI links to do not open
Source: University of Yamanashi notice (Aug 27, 2026) and 1 more · Sources checked:
Who was affected, and how
Site users: multiple sites on the same server became unavailable. The organization: is reopening each site once it is confirmed safe and publishes a status list. It states the sites did not handle personal information and no leak has been confirmed.
What happened
On a rental server the university contracts, a vulnerability in “JCE,” a Joomla extension used by one site, was used in early June to place a web shell (a program for controlling the server from outside). It is believed to have spread to other sites on the same server by late July; unauthorized accounts and SEO spam were found. The university suspended multiple sites on that server.
Related findings in a KnownFor scan
sec-old-libraryAn outdated JavaScript libraryHow to stop it: Replace the library with a current version.
sec-eolSoftware that is no longer supported is visibleHow to stop it: Apply updates to move to a supported version.
sec-version-exposedSoftware version numbers are visible from outsideHow to stop it: Stop showing version numbers to the outside.
Small and mid-sized business websites, Australia (2026)
Source: iTnews (Jul 10, 2026) and 1 more · Sources checked:
17
weaknesses used (all with fixes available)
Who was affected, and how
Businesses: backdoor files were placed on their sites. The ACSC: urged owners to check for webshells, remove them and then apply updates, and to disable components that cannot be patched right away.
What happened
The Australian Cyber Security Centre (ACSC) warned of an ongoing global campaign using weaknesses in website content management systems (CMS) and their plugins. Files for remote control (webshells) have been placed on many small and mid-sized business websites. The campaign covers 17 weaknesses in WordPress plugins, Craft CMS, Joomla's JCE and others; fixes exist for all of them, some released many months earlier.
Individual businesses were not named.
Related findings in a KnownFor scan
sec-old-libraryAn outdated JavaScript libraryHow to stop it: Replace the library with a current version.
sec-eolSoftware that is no longer supported is visibleHow to stop it: Apply updates to move to a supported version.
sec-version-exposedSoftware version numbers are visible from outsideHow to stop it: Stop showing version numbers to the outside.
Source: Wakayama University notice (Jun 17, 2026) and 1 more · Sources checked:
Who was affected, and how
Visitors: were sent to external sites unrelated to the university. The organization: closed the page, apologized, and said it would review the whole website to prevent a repeat.
What happened
A vulnerability in a tool used for the “virtual tour” on the university website was used so that some pages forwarded visitors to unrelated external sites. It was found on June 12. The university states that no personal or confidential information was leaked.
Related findings in a KnownFor scan
sec-old-libraryAn outdated JavaScript libraryHow to stop it: Replace the library with a current version.
sec-eolSoftware that is no longer supported is visibleHow to stop it: Apply updates to move to a supported version.
Source: Oita University notice (Jun 19, 2026) and 1 more · Sources checked:
Who was affected, and how
People arriving from search: were shown unrelated content under the university’s address. The organization: closed the page, apologized, and said it would review the whole website to prevent a repeat.
What happened
A vulnerability in the software used for the “virtual campus tour” on the university website was used to create malicious URLs that appeared in search results, so content unrelated to the university was shown under its domain. It was found on June 17. The university states that there was no intrusion into its servers, no altered files, and no leak of personal or confidential information.
Related findings in a KnownFor scan
sec-old-libraryAn outdated JavaScript libraryHow to stop it: Replace the library with a current version.
sec-eolSoftware that is no longer supported is visibleHow to stop it: Apply updates to move to a supported version.
JapanGovernment / public bodySpoofed email in your name
Ministry of Internal Affairs alert (May 2026)
Source: INTERNET Watch (Ministry alert) and 1 more · Sources checked:
1Fake email posing as tax offices
2Urges residents to pay by QR-code payment
3Only 1.9% set DMARC to stop it
4The Ministry issues a warning
1.9%
.lg.jp bodies that set DMARC to quarantine or reject fake email (16 of 862)
Who was affected, and how
Residents: they received fake email claiming to be from municipal tax offices and had to tell for themselves whether it was real. Municipalities: their names were the ones being used.
What happened
The Ministry warned about fake email posing as municipal tax offices (e.g. “City Hall, Resident Tax Division”) and urging residents to pay resident tax by QR-code payment. Of 862 .lg.jp organizations (prefectures, cities and wards), only 16 (1.9%) set DMARC to quarantine or reject fake email (survey published March 2026).
Related findings in a KnownFor scan
sec-no-dmarcNo DMARC policy for telling fake email apartHow to stop it: Add a DMARC record to DNS (start with monitoring only).
sec-dmarc-noneDMARC is set to monitor onlyHow to stop it: Move DMARC from monitoring to quarantine.
sec-no-spfNo SPF record to check where email comes fromHow to stop it: Add an SPF record to DNS.
sec-spf-allThe SPF record does not restrict sendersHow to stop it: End the SPF record with “-all” or “~all”.
United KingdomBusiness / schoolCannot reach the right contact
Virgin Media O2, UK (2026)
Source: Virgin Media O2 (Apr 24, 2026) and 1 more · Sources checked:
13%
of Brits shown a fake customer service number via search or AI tools
Who was affected, and how
Customers: some called fake numbers and were scammed. The company: published its research and urged people to use only official numbers.
What happened
UK telecom company Virgin Media O2 warned that search engines and AI tools can show fake customer service numbers. In its research, 13% of Brits (about 1 in 8) had been shown a fake customer service number via search engines or AI tools, and 10% rely on numbers generated by AI tools. The company said it has dealt with fraud cases where customers called such numbers and were scammed. It advises using only numbers listed on official company websites, apps or bills.
Related findings in a KnownFor scan
ai-phone-mismatchAI’s phone number differs from the site
JapanGovernment / public bodySent to a fake siteCannot reach the right contact
Nagoya City (notice updated Mar 2026)
Source: Nagoya City notice on discontinued domains taken by third parties · Sources checked:
1Domains of closed sites
25 taken over by third parties
3May lead to dangerous sites
4The city publishes the list and asks to remove links
5 domains
Domains of the city’s closed sites taken over by third parties
Who was affected, and how
Residents: opening an address that used to be the city’s leads to a site unrelated to the city, which may lead on to dangerous sites. The city: published the list and asked linking sites to remove the links.
What happened
The city published a list of 5 domains of its closed sites that had been taken over by third parties, warning that they are unrelated to the city, may lead to dangerous sites and should not be opened out of curiosity, and asking linking sites to remove the links.
Related findings in a KnownFor scan
ai-gov-unofficial-urlAI gives an unofficial address
ai-gov-dead-linkOfficial pages AI links to do not open
United StatesBusiness / schoolSpoofed email in your name
Microsoft Threat Intelligence, United States (2026)
Source: Microsoft Security Blog (Jan 6, 2026) · Sources checked:
Who was affected, and how
Employees: fake emails that looked like they came from their own organization (voicemails, shared documents, HR notices, password expiry) arrived. Microsoft: recommended properly configuring spoof protections and third-party connectors.
What happened
Microsoft reported that phishing emails appearing to be sent internally from organizations' own domains had seen increased use since May 2025. The emails took advantage of complex mail routing and misconfigured spoof protections, and reached a wide variety of organizations across industries; one campaign was used for financial scams against organizations. Microsoft said strict DMARC reject and SPF hard fail policies help prevent this, while a permissive mode does not protect against spoofed messages.
Related findings in a KnownFor scan
sec-dmarc-noneDMARC is set to monitor onlyHow to stop it: Move DMARC from monitoring to quarantine.
sec-spf-allThe SPF record does not restrict sendersHow to stop it: End the SPF record with “-all” or “~all”.
sec-no-dmarcNo DMARC policy for telling fake email apartHow to stop it: Add a DMARC record to DNS (start with monitoring only).
sec-no-spfNo SPF record to check where email comes fromHow to stop it: Add an SPF record to DNS.
Kyoto University, Graduate School of Letters Library, Japan (2025)
Source: Kyoto University Graduate School of Letters notice (Nov 26, 2025) and 1 more · Sources checked:
About 100
articles with malicious scripts embedded
Who was affected, and how
Visitors: may have seen suspicious pop-ups or redirects and were asked to scan their devices. The organization: closed the site; the temporary site has no site search or thesis search. It states no personal information was leaked.
What happened
A vulnerability in the library’s website was used to embed malicious scripts in about 100 articles published between March 2016 and February 2025. Visitors between February 6 and November 13, 2025 may have seen suspicious ads or been forced to external sites. The university closed the site, switched to a simple temporary site, and said it would rebuild it with clean copies of the CMS core, theme and plugins.
Related findings in a KnownFor scan
sec-old-libraryAn outdated JavaScript libraryHow to stop it: Replace the library with a current version.
sec-eolSoftware that is no longer supported is visibleHow to stop it: Apply updates to move to a supported version.
Source: Tokyo University of Foreign Studies notice (Sep 19, 2025) and 1 more · Sources checked:
Who was affected, and how
Visitors during the period: could be sent to online casino sites and were asked to update security software and run a virus scan. The organization: took the server offline and said it would strengthen monitoring and configuration management. It states the server held no personal information of students or staff.
What happened
A server publishing research from the Research Institute for Languages and Cultures of Asia and Africa was accessed through a vulnerability in its content management system (CMS), and some pages were altered to forward visitors to online casino sites. The possible impact period was June 5 to August 8, 2025. The university took the server offline and said it would fix the vulnerability and remove the altered files before reopening.
Related findings in a KnownFor scan
sec-eolSoftware that is no longer supported is visibleHow to stop it: Apply updates to move to a supported version.
sec-old-libraryAn outdated JavaScript libraryHow to stop it: Replace the library with a current version.
sec-version-exposedSoftware version numbers are visible from outsideHow to stop it: Stop showing version numbers to the outside.
Source: Suruga-ya (Dec 4, 2025) and 1 more · Sources checked:
30,431
cards whose data may have leaked
Who was affected, and how
Customers: card details and contact information may have leaked. The organization: it reported to the Personal Information Protection Commission and the police, had outside experts investigate, and asked card companies not to charge customers for reissuing cards.
What happened
Through unauthorized access that used a weakness in a monitoring tool, the JavaScript for the payment page was altered. Data of 30,431 cards (29,932 customers) used from July 23 to August 8, 2025 may have leaked, including card numbers, expiry dates and security codes as well as names, addresses, phone numbers and email addresses. Card payments were stopped on August 8.
The source states the cause was altered JavaScript for the payment page. It does not mention CSP.
Related findings in a KnownFor scan
sec-headersProtective headers are missingHow to stop it: Add the protective headers.
United States, IndiaBusiness / schoolCannot reach the right contact
Google AI Overviews, US and India (2025)
Source: Android Central via Yahoo News (Aug 18, 2025) · Sources checked:
Who was affected, and how
Callers: some spoke to scammers believing they had reached the company, and one shared card details. Google: said it was aware and was reported to have acted on the numbers it identified.
What happened
Users reported that phone numbers shown in Google's AI Overviews led to scammers instead of the company. In the US, a person looking for Royal Caribbean's customer service number called the number shown and was tricked into sharing credit card details. In India, a person searching for Swiggy Instamart's customer care number was given a number, although the company has no phone support, only chat. Google was reported to be aware of the issue and to have taken action against a few numbers it identified.
Related findings in a KnownFor scan
ai-phone-mismatchAI’s phone number differs from the site
of AI-suggested login domains not owned by the brand
Who was affected, and how
Users: login addresses given by AI were fake pages or domains owned by others. The researcher: published the results and examples.
What happened
Security company Netcraft asked an AI model (GPT-4.1 family), in plain language, for the login website of 50 brands in finance, retail, tech and utilities. Of the 97 domains suggested, 66% belonged to the brand, 29% were unregistered, parked or inactive, and 5% belonged to unrelated businesses, so 34% were not brand-owned. In a separate case, the AI search engine Perplexity listed a convincing fake Wells Fargo page as the login link, above the real site.
Related findings in a KnownFor scan
ai-gov-unofficial-urlAI gives an unofficial address
AustraliaGovernment / public bodySpoofed email in your name
Australian Taxation Office, Australia (2025)
Source: Australian Taxation Office (updated Jun 12, 2025) · Sources checked:
300%+
rise in reports of ATO email scams (year on year)
Who was affected, and how
Businesses and the public: fake messages in the ATO's name arrived, trying to trick them into handing over personal information. The ATO: shared simple steps (stop, check, protect) and where to verify a message.
What happened
The Australian Taxation Office said reports of email scams impersonating the ATO had increased by over 300% compared with the same time the year before. It noted that scam reports generally rise at tax time, when people expect to hear from the ATO. The ATO reminded people that it will never send an unsolicited message with a link asking them to return personal information or log into its online services.
The source does not mention sender settings such as DMARC. It is cited as an example of fake email in an organization's name.
Related findings in a KnownFor scan
sec-no-dmarcNo DMARC policy for telling fake email apartHow to stop it: Add a DMARC record to DNS (start with monitoring only).
sec-dmarc-noneDMARC is set to monitor onlyHow to stop it: Move DMARC from monitoring to quarantine.
South KoreaGovernment / public bodySpoofed email in your name
National Tax Service, South Korea (2025)
Source: Korea.kr policy briefing, National Tax Service (Jun 27, 2025) and 1 more · Sources checked:
Who was affected, and how
Taxpayers: hacking emails arrived using the National Tax Service's own domain. The National Tax Service: launched a service on Hometax to check what it really sent.
What happened
South Korea's National Tax Service said it had become harder to tell real messages from fake ones, as hacking emails were being sent even using its own domain (@nts.go.kr). From June 27, 2025, it began a service on its Hometax tax site that lets people check whether an email or text message was really sent by the National Tax Service.
The source does not mention settings such as DMARC. It is cited as an example of fake email using an organization's own domain.
Related findings in a KnownFor scan
sec-no-dmarcNo DMARC policy for telling fake email apartHow to stop it: Add a DMARC record to DNS (start with monitoring only).
sec-dmarc-noneDMARC is set to monitor onlyHow to stop it: Move DMARC from monitoring to quarantine.
NetherlandsGovernment / public bodyCannot reach the right contact
Municipality of Dantumadiel, Netherlands (2025)
Source: NOS (May 19, 2025) and 1 more · Sources checked:
36
emails meant for the municipality received in just over a week
Who was affected, and how
Residents: emails meant for the municipality reached a third party renting the domain. The municipality: bought the .nl domain and redirected it to its official site.
What happened
Dantumadiel has used dantumadiel.frl since 2017 but had never registered the similar dantumadiel.nl. When local broadcaster Omrop Fryslân rented the .nl domain, it received 36 emails meant for the municipality within just over a week, including citizen service numbers (BSN), objections and youth-care information. The municipality itself had also sent mail to that address and printed it in eight issues of its bulletin between July 2024 and March 2025. The municipality then bought the .nl domain and redirected it to its official site.
Related findings in a KnownFor scan
ai-namesakeA same-name site is cited
ai-gov-unofficial-urlAI gives an unofficial address
JapanGovernment / public bodyDefacementSite unavailableFoothold
Shiga Prefectural Library, Japan (2025)
Source: Shiga Prefectural Board of Education: reopening notice and 1 more · Sources checked:
1Brute-force traces and missing updates
2Website defaced 3 times
3All pages offline for ~36 days
4Catalog search and reservations by phone
~36 days
How long the website was offline
Who was affected, and how
Library users: for about 36 days the website was closed, and catalog search and reservations were handled by phone instead of online. The prefecture: closure, investigation and an apology.
What happened
The website was defaced three times and all pages were taken offline for about 36 days; catalog search and reservations were handled by phone. According to the prefecture, there were traces of repeated ID/password attempts (brute force) on the management software, and the latest updates had not been applied to some software. The prefecture apologized for the long disruption.
Related findings in a KnownFor scan
sec-eolSoftware that is no longer supported is visibleHow to stop it: Apply updates to move to a supported version.
sec-old-libraryAn outdated JavaScript libraryHow to stop it: Replace the library with a current version.
sec-version-exposedSoftware version numbers are visible from outsideHow to stop it: Stop showing version numbers to the outside.
Students and others: their personal data was posted on social media. The universities: Korea's Personal Information Protection Commission fined Soonchunhyang 193 million won and ordered corrections (including applying the 2017 patch), and fined Kyungsung 42.8 million won.
What happened
On Soonchunhyang University's main homepage, a weakness in its server software (WebLogic) was used to place a malicious file. More than 2,000 records, including names, departments, student IDs, addresses and contact details, were taken and posted on social media. A patch Oracle released in October 2017 had not been applied for about six years. Kyungsung University's portal was attacked the same way.
Related findings in a KnownFor scan
sec-version-exposedSoftware version numbers are visible from outsideHow to stop it: Stop showing version numbers to the outside.
sec-eolSoftware that is no longer supported is visibleHow to stop it: Apply updates to move to a supported version.
NHN Commerce legacy shop software, South Korea (2024)
Source: Korea Economic Daily (Jan 29, 2026) · Sources checked:
17 businesses
sites still on the old system that leaked
Who was affected, and how
Shoppers: their order details leaked. The company: reported to the Commission within 72 hours but was late in notifying the shops, and was ordered to publish the penalty on its website.
What happened
The cart pages of “e-Namu”, a legacy online-shop system more than 10 years old, were attacked, and 122 orderers' personal records leaked from the sites of 17 businesses that used it. Most shops had moved to a newer system, but a few small businesses kept using the old one. Korea's Personal Information Protection Commission fined NHN Commerce 8.7 million won, among other penalties, for neglecting technical support for the legacy system.
Related findings in a KnownFor scan
sec-eolSoftware that is no longer supported is visibleHow to stop it: Apply updates to move to a supported version.
sec-old-libraryAn outdated JavaScript libraryHow to stop it: Replace the library with a current version.
sec-version-exposedSoftware version numbers are visible from outsideHow to stop it: Stop showing version numbers to the outside.
Source: The Register (Jul 9, 2024) · Sources checked:
~half a day
length of the outage (as reported)
Who was affected, and how
Data users: saw warnings, and API integrations were at risk of stopping. Elexon: renewed the certificate.
What happened
The TLS certificate for Elexon’s Insights Solution (data.elexon.co.uk), the main channel for operational data on GB electricity balancing and settlement, was valid until July 8, 2024, and then expired, so browsers showed a certificate warning. API integrations could also stop working. The certificate was renewed around lunchtime on July 9, after about half a day of outage (according to The Register).
Related findings in a KnownFor scan
sec-cert-expiringThe certificate expires soon (or has expired)How to stop it: Renew the certificate and set it to renew automatically.
South KoreaGovernment / public bodySent to a fake site
Ministry of the Interior and Safety, South Korea (2024)
Source: BizWatch (Jul 4, 2024) · Sources checked:
356
listed official sites that would not open (of 5,826)
Who was affected, and how
People using the official directory: were sent to pages that did not open or to unrelated gambling and adult sites. The ministry: deleted or changed the listed addresses after the report.
What happened
The Ministry of the Interior and Safety's directory of official government websites listed 5,826 sites, but a news investigation found 356 would not open, 5 had wrong addresses and 2 were old addresses now held by others. The 2 were or.kr addresses left empty after the institutions moved to go.kr, and they led to an adult goods shop and an illegal gambling site. After the report, the ministry deleted or changed those links.
Related findings in a KnownFor scan
ai-gov-unofficial-urlAI gives an unofficial address
ai-gov-dead-linkOfficial pages AI links to do not open
United StatesBusiness / schoolSpoofed email in your name
FBI, State Department and NSA advisory, United States (2024)
Source: FBI, U.S. Department of State and NSA (May 2, 2024) · Sources checked:
Who was affected, and how
Recipients: emails arrived posing as real journalists and researchers. The agencies: published signs to spot these emails and mitigation steps (DMARC settings) for organizations whose names could be used.
What happened
The FBI, the U.S. Department of State and the NSA jointly warned that North Korean actors known as Kimsuky were exploiting improperly configured DMARC policies to send spoofed email. The emails posed as real journalists, academics and other experts in East Asian affairs. The advisory explains that without properly configured DMARC, spoofed email can be sent as if it came from a legitimate domain, and it recommends setting DMARC to quarantine (p=quarantine) or reject (p=reject).
Related findings in a KnownFor scan
sec-no-dmarcNo DMARC policy for telling fake email apartHow to stop it: Add a DMARC record to DNS (start with monitoring only).
sec-dmarc-noneDMARC is set to monitor onlyHow to stop it: Move DMARC from monitoring to quarantine.
BelgiumGovernment / public bodyCannot reach the right contact
Municipality of Pelt, Belgium (2024)
Source: VRT NWS (May 22, 2024) · Sources checked:
107
expired public-body domains bought by a researcher
Who was affected, and how
People using the old address: mail and visits could reach owners unrelated to the municipality. The municipality: said it communicates only via gemeentepelt.be and started an awareness campaign.
What happened
After two towns merged into Pelt in 2019, the former town's domain overpelt.be was not renewed and passed to unknown owners, who now also control email addresses ending in @overpelt.be; the site now looks like a blog on various topics. The municipality noticed in 2022 and tried to buy it back, without success. A security researcher separately bought 107 expired domains that had belonged to welfare agencies, police zones and similar bodies, to raise awareness.
Related findings in a KnownFor scan
ai-gov-unofficial-urlAI gives an unofficial address
The public: fake messages offering tax rebates arrived. HMRC: responded to the referrals and reported 26,443 malicious web pages to internet service providers to be taken down.
What happened
HMRC said it responded to 207,800 referrals from the public about suspicious contact in the year to January (181,873 the year before). More than 79,000 of them offered bogus tax rebates. Scammers use email, phone calls and texts that mimic government messages to look authentic. HMRC reminded people that it will not email, text or phone to tell them they are due a refund.
The source does not mention sender settings such as DMARC. It is cited as an example of fake email in an organization's name.
Related findings in a KnownFor scan
sec-no-dmarcNo DMARC policy for telling fake email apartHow to stop it: Add a DMARC record to DNS (start with monitoring only).
sec-dmarc-noneDMARC is set to monitor onlyHow to stop it: Move DMARC from monitoring to quarantine.
The customer: relied on the chatbot and bought full-fare tickets. The airline: was ordered by the tribunal to pay and said it would update the chatbot.
What happened
The chatbot on Air Canada's website said a bereavement fare could be claimed within 90 days of the ticket being issued, so the customer bought full-fare tickets. In fact, bereavement rates did not apply to completed travel, as explained on another page of the website. The airline argued it could not be held liable for the chatbot's answers, but British Columbia's Civil Resolution Tribunal found the airline did not take reasonable care to ensure its chatbot was accurate and ordered it to pay.
Not a phone number or address case: the AI answer differed from the official page.
NetherlandsGovernment / public bodySpoofed email in your name
Dutch government standards forum survey, Netherlands (2023)
Source: Forum Standaardisatie (meeting paper, Dec 13, 2023) · Sources checked:
81%
government domains with a DMARC policy (mid-2023)
Who was affected, and how
Public bodies:19% of domains did not yet have a strict DMARC policy in place to prevent phishing in their name. The forum: measured and published the figures for each type of public body.
What happened
A survey by the Dutch government's standards forum (Forum Standaardisatie) found that, of 2,661 domains of central government, municipalities and other public bodies, 81% had a DMARC policy in mid-2023. The report explains that DMARC, DKIM and SPF together prevent email spoofing and make phishing in the name of government organizations harder. It concludes that 19% of the domains still needed a strict DMARC policy to prevent phishing email in the name of government organizations. For municipalities (363 domains), the figure was 90%.
Related findings in a KnownFor scan
sec-dmarc-noneDMARC is set to monitor onlyHow to stop it: Move DMARC from monitoring to quarantine.
sec-no-dmarcNo DMARC policy for telling fake email apartHow to stop it: Add a DMARC record to DNS (start with monitoring only).
sec-no-spfNo SPF record to check where email comes fromHow to stop it: Add an SPF record to DNS.
25 acquired by third parties via auctions and similar
3They lead to sites unrelated to the prefecture
4A warning and requests to remove links
5 domains
Domains of discontinued prefectural sites acquired by third parties
Who was affected, and how
People opening the prefecture’s old addresses: they reach sites unrelated to the prefecture. The prefecture: a public warning and requests to linking sites to remove the links.
What happened
Five domains of discontinued prefectural sites were acquired by third parties through auctions and similar means. The prefecture warned they were unrelated to it and asked linking sites to remove the links.
Related findings in a KnownFor scan
ai-gov-unofficial-urlAI gives an unofficial address
Source: Meguro City press release (Jul 28, 2023) and 1 more · Sources checked:
1A fault in an online application service
25 applications reach another municipality
3Personal data of 51 people
4The city apologizes and asks for deletion
51 people
Personal data in applications that reached another municipality
Who was affected, and how
Residents and businesses who applied (personal data of 51 people): their applications reached another municipality. The city: an apology and a request for deletion.
What happened
A fault in an online application service sent 2 residents’ subsidy applications and 3 businesses’ grant applications (personal data of 51 people) to another municipality using the same service. The city apologized and asked for deletion (it states this occurred within a closed inter-government network, with no leak outside).
The cause was not encryption, but it is an example of application data reaching others.
Related findings in a KnownFor scan
sec-form-insecureForms that send data without protectionHow to stop it: Make the form send to an https address.
sec-no-httpsNo redirect from http to httpsHow to stop it: Add a redirect from http to https.
The agency: its web servers were entered and files were placed on them. The agency removed the first server from the network within 24 hours of the alert. CISA published an advisory (Dec 5, 2023).
What happened
In June–July 2023, two public-facing web servers at a U.S. federal agency were broken into. Both ran outdated versions of Adobe ColdFusion (2016 and an early 2021 release). CISA stated that both servers were running outdated versions of software.
The agency was not named. CISA says there is no evidence confirming that data was taken.
Related findings in a KnownFor scan
sec-eolSoftware that is no longer supported is visibleHow to stop it: Apply updates to move to a supported version.
sec-version-exposedSoftware version numbers are visible from outsideHow to stop it: Stop showing version numbers to the outside.
United StatesGovernment / public bodySent to a fake site
Maryland Motor Vehicle Administration, US (2023)
Source: The Baltimore Banner (Jun 9, 2023) · Sources checked:
~800,000
license plates carrying the address
Who was affected, and how
People who typed the plate address: were sent to a casino promotion site. The MVA: recovered the domain and redirected it to its homepage.
What happened
For several months, the commemorative web address printed on about 800,000 Maryland license plates (starspangled200.org) redirected to a site promoting online casinos in the Philippines. The domain originally belonged to a state commission for the commemoration and had changed hands several times since 2016. The Motor Vehicle Administration worked with the state IT department and a domain broker to recover it, and it now redirects to the MVA homepage.
Related findings in a KnownFor scan
ai-gov-unofficial-urlAI gives an unofficial address
Site visitors: they could be sent automatically to a malicious site. The university: took the site down to investigate.
What happened
A weakness in the site’s content management system was used to rewrite pages so that visitors were automatically sent to a malicious site. The site was taken down for investigation.
Related findings in a KnownFor scan
sec-eolSoftware that is no longer supported is visibleHow to stop it: Apply updates to move to a supported version.
sec-old-libraryAn outdated JavaScript libraryHow to stop it: Replace the library with a current version.
sec-version-exposedSoftware version numbers are visible from outsideHow to stop it: Stop showing version numbers to the outside.
Customers worldwide: lost internet access. SpaceX: stated the cause and checked for other weak points.
What happened
Over a weekend in April 2023, the Starlink satellite internet service had a multi-hour global outage. SpaceX’s Elon Musk posted that it was caused by an expired ground station certificate and that the company was checking the system for other single-point vulnerabilities.
This was a ground station certificate, not a website certificate. It is cited as an example of a service stopping when a certificate expires.
Request by Japan's MIC, National Police Agency and METI, Japan (2023)
Source: Ministry of Internal Affairs and Communications (Feb 1, 2023) · Sources checked:
Who was affected, and how
Card users: phishing emails in card companies' names led them to fake sites where card numbers were stolen, and such cases were increasing. The three agencies: asked card companies to adopt DMARC with a reject policy.
What happened
Japan's Ministry of Internal Affairs and Communications, the National Police Agency and the Ministry of Economy, Trade and Industry asked credit card companies to strengthen anti-phishing measures, as phishing emails posing as card companies were frequently leading users to fake sites to steal card numbers. Noting that phishing emails often spoof domain names, they asked companies to add DMARC to all public domains, including ones that send no email, and to run it with a policy that has receivers reject spoofed email.
Related findings in a KnownFor scan
sec-no-dmarcNo DMARC policy for telling fake email apartHow to stop it: Add a DMARC record to DNS (start with monitoring only).
sec-dmarc-noneDMARC is set to monitor onlyHow to stop it: Move DMARC from monitoring to quarantine.
Source: CISA, FBI and MS-ISAC advisory AA23-074A (revised Jun 15, 2023) · Sources checked:
2013
year of the component version in use
Who was affected, and how
The agency: unauthorized files were placed and run on its web server. CISA and partners: published the findings and the fixes, including updating the component.
What happened
On a U.S. federal agency's web server, a weakness was used in a component (Telerik UI for ASP.NET AJAX) still running a 2013 version. From November 2022 to early January 2023, multiple cyber attackers placed and ran files on the server. According to the vendor, builds before early 2020 have this weakness.
The agency was not named. In April 2023, a weakness in an old version of the same component was also used at a second agency.
Related findings in a KnownFor scan
sec-old-libraryAn outdated JavaScript libraryHow to stop it: Replace the library with a current version.
sec-version-exposedSoftware version numbers are visible from outsideHow to stop it: Stop showing version numbers to the outside.
Source: Amazon EU (Nov 16, 2022) · Sources checked:
50%+
share of reported scams that were fake order confirmations
Who was affected, and how
Customers: fake order confirmations and other messages in Amazon's name arrived. Amazon: pursued takedowns of phishing sites and added verification so real emails show its logo.
What happened
Amazon said that fake order confirmations made up more than 50% of the Amazon impersonation scams reported by its customers. That year it had initiated takedowns of more than 20,000 phishing websites and 10,000 phone numbers. Earlier the same year it implemented email verification technology across more than 20 countries, so that in Gmail, Yahoo! and other common providers the Amazon smile logo icon shows an email is really from Amazon.
The source does not name DMARC. It is cited as an example of a company adopting sender verification.
Related findings in a KnownFor scan
sec-dmarc-noneDMARC is set to monitor onlyHow to stop it: Move DMARC from monitoring to quarantine.
sec-no-dmarcNo DMARC policy for telling fake email apartHow to stop it: Add a DMARC record to DNS (start with monitoring only).
Visitors: saw an error and could not view the website. The company: apologized and said it would strengthen its management.
What happened
From midnight on June 1 until 12:04 on June 2, 2022, visitors to the company website (www.gyosei-system.co.jp) saw an error. The cause was an expired SSL certificate. The company apologized and said it would strengthen its management.
Related findings in a KnownFor scan
sec-cert-expiringThe certificate expires soon (or has expired)How to stop it: Renew the certificate and set it to renew automatically.
Source: BleepingComputer (Jan 14, 2022) and 1 more · Sources checked:
about 15
government sites defaced
Who was affected, and how
Citizens: some sites stayed unavailable for a time, and the foreign ministry posted on social media instead. The government: took the sites down to restore them and stated that no personal data had leaked.
What happened
On January 14, 2022, about 15 government websites, including the Ministry of Foreign Affairs and the Cabinet of Ministers portal, were defaced and taken offline. Ukraine's CERT said a weakness in October CMS, used to manage the sites, was the likely way in. A fix for that weakness had been released in August 2021.
Related findings in a KnownFor scan
sec-old-libraryAn outdated JavaScript libraryHow to stop it: Replace the library with a current version.
sec-version-exposedSoftware version numbers are visible from outsideHow to stop it: Stop showing version numbers to the outside.
sec-eolSoftware that is no longer supported is visibleHow to stop it: Apply updates to move to a supported version.
Source: Singapore PDPC decision [2023] SGPDPCS 3 and 1 more · Sources checked:
6,241 people
people whose login details were captured
Who was affected, and how
Customers: login details and card details were captured. The company: notified affected people, improved its security and moved to upgrade to Magento 2.
What happened
Malicious code injected into the online store captured the email addresses and passwords of 6,241 people when they logged in, and the name, card number, expiry date and CVV of another 98 people. The store ran on Magento 1.9 and four security patches released by Adobe had not been applied; support for Magento 1 had ended on 30 June 2020. Singapore's Personal Data Protection Commission (PDPC) imposed a financial penalty of S$8,000 and directed the company to upgrade to a supported version within 6 months.
Related findings in a KnownFor scan
sec-eolSoftware that is no longer supported is visibleHow to stop it: Apply updates to move to a supported version.
sec-version-exposedSoftware version numbers are visible from outsideHow to stop it: Stop showing version numbers to the outside.
sec-old-libraryAn outdated JavaScript libraryHow to stop it: Replace the library with a current version.
Source: UK ICO (Jul 30, 2024) and 1 more · Sources checked:
about 40 million
people whose names and addresses were reachable
Who was affected, and how
Voters: the names and addresses of about 40 million people were reachable (the ICO says it found no evidence of direct harm). The Commission: received a reprimand from the ICO and began modernising its infrastructure, tightening password rules and adding multi-factor authentication for all users.
What happened
In August 2021, cyber attackers got into the Electoral Commission's Microsoft Exchange server and, until October 2022, could reach the names and home addresses of about 40 million people on the Electoral Register. According to the UK's data protection regulator (ICO), fixes for the weaknesses used had been released in April and May 2021 but had not been applied. Password rules were also inadequate.
The way in was an internet-facing mail server, not the public website. It is shown as an example of internet-facing software left without updates.
Related findings in a KnownFor scan
sec-version-exposedSoftware version numbers are visible from outsideHow to stop it: Stop showing version numbers to the outside.
sec-eolSoftware that is no longer supported is visibleHow to stop it: Apply updates to move to a supported version.
Source: Google incident report (Feb 2021) and 1 more · Sources checked:
4 h 22 min
total duration of failed calls
Who was affected, and how
Users: devices that newly connected could not make or receive calls. Google: rolled out new certificates as an emergency and published prevention steps.
What happened
On February 15, 2021 (US Pacific time), an issue with updating certificate configurations caused the active TLS certificate in Google Voice’s frontend systems to expire. Devices trying to connect or reconnect could not do so and could not make or receive VoIP calls, for a total of 4 hours 22 minutes. Google apologized and listed steps including more alerts for upcoming certificate expiry and better automated tooling for certificate rotation.
Related findings in a KnownFor scan
sec-cert-expiringThe certificate expires soon (or has expired)How to stop it: Renew the certificate and set it to renew automatically.
United StatesGovernment / public bodySystem stopped
State of California, United States (2020)
Source: The Register (Aug 11, 2020) · Sources checked:
~300,000
test results left unprocessed or uncounted
Who was affected, and how
The state and counties: test results did not arrive and cases were not counted correctly. The state: the certificate was renewed and officials explained what happened.
What happened
A digital certificate on a system that receives results from a medical lab was not renewed on July 31 and stayed invalid until August 4. Together with a server failure that began on July 25, around 300,000 COVID-19 test results went unprocessed or uncounted. The state's Health and Human Services secretary explained what had happened.
This was a certificate on a data-receiving system, not a public website. It is cited as an example of a system stopping when a certificate expires.
Residents: card details entered when paying may have been read. The organizations: the source does not describe the cities' response.
What happened
In eight cities across three US states, JavaScript was injected into the payment page of the Click2Gov sites residents use to pay for services such as utilities. Card numbers, CVVs, expiry dates, names and addresses entered there were sent to a remote server. The researchers believe it began around April 10, 2020. Five of the eight cities had also been affected in 2018.
The source states the cause was script injected into the payment page. It does not mention CSP. The source is a security firm's report and does not name the cities.
Related findings in a KnownFor scan
sec-headersProtective headers are missingHow to stop it: Add the protective headers.
Users: could not sign in or use Teams. Microsoft: explained the cause and deployed an updated certificate.
What happened
On the morning of February 3, 2020, Microsoft Teams was unavailable for about three hours. Users trying to sign in saw errors saying an HTTPS connection could not be established. Microsoft said an authentication certificate had expired, and restored the service by deploying an updated certificate.
Related findings in a KnownFor scan
sec-cert-expiringThe certificate expires soon (or has expired)How to stop it: Renew the certificate and set it to renew automatically.
Customers: card details and contact information they typed may have been read. The organization: it reported the card numbers to the card brands and offered 12 months of free identity protection.
What happened
On October 7, 2019, a third party added unauthorized code to two pages on macys.com: the checkout page and the My Account wallet page. The code captured the names, addresses, phone numbers, email addresses, card numbers, security codes and expiry dates customers typed there. A suspicious connection to another website was noticed on October 15, and the code was removed the same day. Use on mobile devices and the app was not involved.
The source states the cause was unauthorized code added to the pages. It does not mention CSP.
Related findings in a KnownFor scan
sec-headersProtective headers are missingHow to stop it: Add the protective headers.
Source: New York State Attorney General (May 18, 2021) · Sources checked:
3 years
from the fix being issued to the attack
Who was affected, and how
Customers: card details were taken, and notices came more than a year later. The company: offered up to 12 months of identity theft protection, agreed a $200,000 settlement with the New York Attorney General ($100,000 suspended on conditions) and committed to overhaul its security, including patch management.
What happened
In July 2019, a known weakness in the online store's checkout was used to collect card customers' names, billing addresses, card expiry dates and security codes. According to the forensic investigator, a software patch for the problem had been issued three years before the attack. The site was patched on July 10, 2020, so purchases over about a year were affected. About 320,000 consumers nationwide were affected.
Related findings in a KnownFor scan
sec-old-libraryAn outdated JavaScript libraryHow to stop it: Replace the library with a current version.
sec-version-exposedSoftware version numbers are visible from outsideHow to stop it: Stop showing version numbers to the outside.
United StatesGovernment / public bodySite unavailable
US federal .gov websites, United States (2019)
Source: The Register (Jan 11, 2019) and 1 more · Sources checked:
more than 80
.gov TLS certificates that expired and were not renewed
Who was affected, and how
Site users: browsers showed warnings, and some sites could not be opened. The organizations: certificates were not renewed during the shutdown.
What happened
In January 2019, during the US government shutdown, more than 80 TLS certificates used on .gov websites expired and were not renewed (according to Netcraft). Browsers showed warnings on sites of the Department of Justice, NASA, the Court of Appeals and others. The Justice Department site ows2.usdoj.gov, whose certificate expired on December 17, 2018, was on the HSTS preload list, so Chrome and Firefox did not allow users past the warning and the site could not be opened.
Related findings in a KnownFor scan
sec-cert-expiringThe certificate expires soon (or has expired)How to stop it: Renew the certificate and set it to renew automatically.
Source: Ericsson (Dec 6, 2018) and 1 more · Sources checked:
11 countries
other countries where similar faults were reported at almost the same time
Who was affected, and how
Users: mobile phones, and home phones on the same network, were unavailable or hard to use. Ericsson: announced the cause and began decommissioning the faulty software.
What happened
From about 1:39 pm to 6:04 pm on December 6, 2018, SoftBank and Y!mobile LTE mobile service was unavailable or hard to use across Japan. Ericsson, the equipment maker, said its initial analysis pointed to an expired certificate in the software, and its CEO apologized. Similar faults were reported at operators in 11 other countries using Ericsson equipment at almost the same time.
This was a certificate inside mobile network equipment, not a website certificate. It is cited as an example of a system stopping when a certificate expires.
Customers: names, addresses, card numbers and CVV numbers may have been read. The organization: it contained the code and, the next day (6 September), notified the ICO, banks, payment schemes and customers.
What happened
From 22 June to 5 September 2018, a cyber attacker got into the company network and edited a JavaScript file on britishairways.com. For 15 days from 21 August, a copy of the card details customers entered was sent to a separate domain controlled by the cyber attacker (BAways.com). The UK Information Commissioner's Office (ICO) said the data of approximately 429,612 people may have been accessed, and issued a £20m penalty in October 2020.
The source states the cause was an edited JavaScript file on the website. It does not mention CSP (the setting that limits which scripts can run). It is cited as an example of input being read by a script running in the page.
Related findings in a KnownFor scan
sec-headersProtective headers are missingHow to stop it: Add the protective headers.
Customers: card details and other input were collected. The organization: it removed the chat bot and notified those affected.
What happened
A cyber attacker inserted malicious code into the JavaScript of a third-party chat bot that the company had also placed on its payment page. The code collected what customers typed, including names, card numbers, expiry dates and CVV numbers. 9.4 million people in Europe (1.5 million in the UK) were notified as potentially affected. The UK ICO issued a £1.25m penalty in November 2020.
The ICO said the risk of third-party scripts on payment pages was well known, and named measures such as SRI (checking that a script has not been altered) and CSP (setting where scripts may load from). The company confirmed a content security policy was not used before the breach.
Related findings in a KnownFor scan
sec-headersProtective headers are missingHow to stop it: Add the protective headers.
sec-no-sriScripts loaded from outside lack tamper protection (SRI)How to stop it: Add tamper protection (integrity) to scripts loaded from outside.
People downloading: they received software bundled with spyware. The organizations: Opera and CCleaner had fixed their downloads by the time of the report.
What happened
On the network of a Turkish telecom operator (Türk Telekom), people trying to download software from official sites such as Avast, CCleaner, Opera and 7-Zip were switched to versions bundled with spyware. The report says this was possible because these sites sent users to unencrypted (HTTP) downloads by default, even where HTTPS was supported. It says hundreds of users in Turkey and Syria were affected.
The source is a report by a research lab (Citizen Lab). It calls for wide use of HTTPS, especially on software download sites.
Related findings in a KnownFor scan
sec-no-httpsNo redirect from http to httpsHow to stop it: Add a redirect from http to https.
United KingdomGovernment / public bodyDevice used without consent
UK public-sector websites (2018)
Source: UK NCSC (Feb 11, 2018) and 1 more · Sources checked:
4,000+
sites affected
Who was affected, and how
Visitors: their devices were used without their knowledge. The organizations: the add-on was taken offline, and the ICO closed its website while it investigated.
What happened
On 11 February 2018, the JavaScript of a text-to-speech add-on (Browsealoud) loaded by many sites was altered, and code that mined cryptocurrency ran on visitors' devices. More than 4,000 sites were affected, including the UK ICO, NHS trusts and local councils. According to the UK National Cyber Security Centre (NCSC), no money was taken from users, but device performance and battery life may have been affected.
The NCSC advised deciding carefully on third-party JavaScript, and named SRI (checking that a script has not been altered) and CSP (setting where scripts may load from). It noted that several independent researchers wrote that a well-defined CSP would have blocked this attack.
Related findings in a KnownFor scan
sec-headersProtective headers are missingHow to stop it: Add the protective headers.
sec-no-sriScripts loaded from outside lack tamper protection (SRI)How to stop it: Add tamper protection (integrity) to scripts loaded from outside.
Not a web incident (outside what a scan covers). Listed for reference on what an organization faces afterwards.
1A contractor loses a USB drive
2Personal data of all ~460,000 residents
3The mayor apologizes at a press conference
4Over 16,000 inquiry calls in a day
~460,000 residents
Personal data on the lost USB drive
Who was affected, and how
All ~460,000 residents: a USB drive with their personal data was lost. The city: a press conference and more than 16,000 inquiry calls in one day (according to press reports).
What happened
A contractor lost a USB drive holding personal data of all ~460,000 residents. The mayor apologized at a press conference; according to press reports, phone inquiries after the conference exceeded 16,000 in one day. The mayor’s bonus (about ¥1.95 million) was cut in full (unprecedented, according to the city).
If the same kind of weakness is found, the report shows it in five levels.
Like Japan’s disaster alert levels, each level number is paired with the action to take. The level is decided by machine from the protection check.
Cyber attackers break in to steal, destroy or demand ransom. They sweep sites nationwide by machine, 24 hours a day, 365 days a year (Japan’s police sensors receive 13,687 such accesses per address per day) and may exploit vulnerabilities they find.
LevelAction to takeWhat it means
5Stop it this weekSend the request todayA weakness confirmed as exploited in real attacks is visible / customers’ input is sent unencrypted. Cyber attackers’ automated sweeps reach every site every day; once found, this becomes a way to break in or to read what people type
▼▼ By level 4, always decide who is responsible and by when ▼▼
4Fix it this monthLeft as is, harm can happen (serious). If cyber attackers find it, it becomes their way in
3Fix it by the next scanNot harmful alone, but links with other weaknesses (warnings combine). Cyber attackers combine weaknesses and use them together
2Put it in the fix planMissing settings that can serve as a foothold (warning, minor). These become clues cyber attackers use to scout
1Keep checkingNothing found within what was checked (this does not mean “safe”). The sweeps go on every day
A sample of the table in a KnownFor report. Which level applies depends on each site’s check.
We write only facts confirmed in the sources. We do not add figures that are not in the sources (such as estimated losses).
We do not blame affected organizations. The cyber attackers are the ones who attacked. Because organizations disclosed what happened, others can prepare.
We do not describe attack methods or publish warnings that single out particular organizations.
Incident texts are KnownFor’s summaries of the sources. Please check the sources for the original wording. We do not copy the text or figures of press articles.
We re-check sources every six months and record the date checked for each incident.
If you notice an error, please tell us through the contact form. We will check, correct it and record the date of the correction.
The incidents listed here are recorded events at other organizations. They do not mean anything happened or will happen to the reader’s organization.
KnownFor is not affiliated with, endorsed or approved by the agencies cited as sources (the US CISA, Japan’s National Police Agency, NICT, IPA and others). Their names are used only to identify sources.
Government materials are summarized and adapted with attribution, in line with each agency’s terms of use (such as Japan’s Public Data License PDL1.0). KnownFor’s defense check passively examines what is visible from outside; it is not a penetration test or a guarantee of security.