657,000 cyberattacks hit Indonesia in 24 hours: Financial and Government sectors face heavy pressure
Around 657,000 cyberattack activities were detected and blocked in Indonesia within a 24-hour period ending on November 8, 2026, equivalent to roughly eight activities every second. Banking, financial services and insurance faced the largest volume at approximately 262,000 activities, followed by government organizations with 102,000 and manufacturing with 81,000. The figures do not mean that 657,000 systems were successfully compromised, but they illustrate the scale at which exposed infrastructure is continuously scanned and tested for weaknesses.
According to Kompas, citing live threat-monitoring data from FortiGuard Labs, the activity affected a broad range of industries, including financial services, government, manufacturing, technology, education, logistics and healthcare.

The headline number is significant, but the nature of the activity is arguably more important. A substantial portion involved attempts associated with vulnerabilities and attack techniques that security teams have known about for years, including Log4j.
For Indonesian organizations, this reinforces a familiar but increasingly urgent security lesson: attackers do not need a brand-new zero-day when an older exposed weakness still works.
Financial services, government and manufacturing faced the Highest Pressure
Based on the figures reported by Kompas, banking, financial services and insurance accounted for approximately 262,000 detected attack activities. Government organizations followed with around 102,000, while manufacturing recorded approximately 81,000.
Other sectors were also affected:
Sector | Detected Attack Activities |
Banking, financial services and insurance | 262,000 |
Government | 102,000 |
Manufacturing | 81,000 |
Technology | 47,000 |
Education | 23,000 |
Construction | 12,000 |
Transportation and logistics | 12,000 |
Agriculture | 10,000 |
Healthcare | 8,500 |
The concentration of activity around financial services is particularly relevant for Indonesia.
Banks, fintech companies, payment operators, digital financial platforms and other financial institutions operate highly connected environments containing customer identities, transaction systems, APIs, mobile applications and sensitive financial information.
Indonesia's regulators have also been placing greater emphasis on cyber resilience. OJK has described cybersecurity as a prerequisite for the sustainability of the digital financial industry, while Bank Indonesia maintains information-security and cyber-resilience requirements for payment system providers and other regulated entities.
The implication is that cybersecurity is no longer only an IT issue. For financial organizations, it increasingly intersects with operational resilience, customer trust, regulatory governance and business continuity.
For additional context on the evolving financial threat landscape, IPSIP Vietnam has also examined six cybersecurity trends affecting banking and financial services in 2026.
Why are government systems still attractive targets?
Government environments recorded approximately 102,000 attack activities in the dataset reported by Kompas.
Public-sector systems can be attractive targets because they may contain citizen information, administrative data, internal documents, public-service portals and connections to other government infrastructure.
The consequences of compromise may also extend beyond data theft.
A legitimate government website that has been compromised can potentially be abused to host malicious content, redirect visitors, distribute malware or create additional credibility for follow-on attacks.
IPSIP Vietnam previously examined this type of risk in a case where hackers abused government websites to distribute malware.
This makes the security of Internet-facing public systems particularly important. Patch management, access control and perimeter security need to be complemented by monitoring capable of identifying suspicious activity after an attacker reaches an exposed service.
Log4j Is still generating large volumes of exploitation activity
One of the most notable figures reported by Kompas involved Apache Log4j Error Log Remote Code Execution, which accounted for approximately 379,000 activities.
Other detected threats included:
React Server Components: approximately 110,000 activities;
GeoServer OGC: approximately 26,000;
SolarWinds SUNBURST Backdoor: approximately 25,000;
additional activity involving SLP Register Service, Hikvision, Apache HTTP Server and Atlassian Server.
This does not mean that every attempt resulted in successful exploitation.
Internet-facing systems are constantly scanned by automated tools, botnets and exploit frameworks searching for vulnerable software versions. But that is exactly why older vulnerabilities remain important.
A vulnerability does not become harmless simply because it is old. It becomes harmless only when the vulnerable exposure has actually been removed, patched or otherwise mitigated.
A forgotten server, outdated appliance, temporary development environment or legacy application can remain exposed long after the rest of an organization has moved forward.
657,000 cyberattacks in Indonesia do not mean 657,000 successful breaches
This distinction is essential when interpreting threat-map statistics. The figures reported in the Indonesian media represent detected or blocked malicious activity. Such telemetry can include scanning, exploit attempts, botnet traffic and other suspicious interactions.
Therefore, 657,000 detected attack activities ≠ 657,000 successful compromises. A single exposed server might receive thousands of automated exploitation requests in a short period of time. Those requests can all appear in security telemetry even if none succeeds.
At the same time, the volume should not be dismissed. It demonstrates how routinely Internet-facing infrastructure is tested by automated attackers.
Organizations should not rely on assumptions such as: “Our company is too small to be targeted.” or: “Nobody knows this server exists.” Automated scanning makes those assumptions increasingly unreliable. Attackers do not necessarily select every target manually; they can simply discover vulnerable assets at scale.
What the numbers mean for organizations operating in Indonesia
The more useful question for businesses is not whether Indonesia experienced exactly 657,000 or some other number of malicious activities.
The more important question is: What happens when the same automated exploitation reaches your infrastructure?
Organizations operating in Indonesia increasingly depend on cloud services, APIs, digital payments, mobile applications, remote access, third-party platforms and connected supply chains.
This means the attack surface is no longer limited to the corporate network perimeter.
For financial institutions in particular, the issue also sits within a broader national focus on digital resilience. OJK has continued to strengthen cybersecurity expectations across the digital financial ecosystem, while Bank Indonesia's regulations emphasize information-system security and cyber resilience for payment-related environments.
Three lessons stand out:
First, asset inventories need to reflect what is actually exposed today. An abandoned cloud instance, old VPN gateway or forgotten staging application can introduce risk even if the primary environment is fully patched.
Second, patching should be prioritized according to exposure and exploitation risk, rather than treated purely as a calendar-based maintenance task.
Third, prevention needs to be connected to detection and response. If exploitation succeeds, the organization should be able to identify what the attacker did next.
Why patch management alone is not enough
Patching remains fundamental, especially when known vulnerabilities are being actively scanned. However, patching alone does not answer every security question.
An organization may have already patched a vulnerable application but still need to know whether exploitation occurred before the update was applied.
Similarly, a vulnerability scanner may confirm that a weakness exists but may not fully demonstrate how that weakness could be combined with poor segmentation, excessive privileges, exposed credentials or weak application logic.
This is where organizations need to think about the broader security lifecycle:
Discover → Validate → Remediate → Monitor → Respond
The purpose is not simply to produce a list of vulnerabilities. The goal is to determine which weaknesses can realistically lead to meaningful compromise.
Detection and incident response still matter after remediation
A patched vulnerability may close the immediate entry point, but security teams should still ask whether compromise happened earlier.
Useful questions include:
Was the vulnerable system exposed during the period of exploitation?
Are there suspicious authentication events?
Did an unknown process execute?
Were new accounts or privileges created?
Did the system communicate with unusual external infrastructure?
Was data accessed or transferred?
Did the attacker move laterally to other systems?
This is why incident response readiness needs to exist before an incident occurs.
Security teams should already know who owns investigation, which systems contain relevant logs, when an incident should be escalated and who has authority to isolate systems or revoke access.
IPSIP Vietnam's analysis of the first 72 minutes of cybersecurity incident response provides additional context on why early investigation and escalation can significantly affect the outcome of an incident.
Where Penetration Testing fits into the response
For organizations exposed to large-scale automated exploitation, Penetration Testing (Pentest) can provide a different type of assurance from ordinary vulnerability scanning.
A vulnerability scanner identifies known weaknesses based on signatures, versions and configuration patterns. A penetration test goes further by evaluating whether those weaknesses can be combined and exploited in a realistic attack path.
For example, a Pentest may help determine whether an attacker could move from an exposed web application to sensitive data, use a weak identity configuration to escalate privileges, or pivot from one compromised system into another network segment.
That distinction matters in the context of the Indonesian threat activity. The threat data shows that attackers are continuously testing exposed infrastructure. Pentest allows organizations to ask the same question from the defensive side:
If an attacker reaches this asset, how far could they actually go? A practical security cycle may therefore look like:
Asset Discovery → Vulnerability Assessment → Pentest → Remediation → Detection → Incident Response
Pentest does not replace patch management, SOC monitoring or EDR/XDR. Instead, it helps validate whether security controls, configurations and privilege boundaries can withstand realistic attack paths.
Organizations reviewing the security of web applications, infrastructure, cloud environments or other critical systems can refer to IPSIP Vietnam's Penetration Testing service to understand the types of environments that can be assessed before defining an appropriate testing scope.
The objective is not to perform Pentest simply because a major cyberattack headline appears. The objective is to identify exploitable weaknesses before attackers find and combine them first.
A practical security checklist for Indonesian organizations
For organizations evaluating their exposure following the Indonesia attack data, the following actions provide a practical starting point:
inventory Internet-facing servers, applications, APIs and remote-access services;
verify operating system, middleware and application versions;
compare exposed systems against vulnerabilities currently seeing exploitation activity;
prioritize remediation for Internet-facing and business-critical assets;
review MFA and privileged-access controls;
analyze firewall, WAF, identity and EDR/XDR logs for suspicious activity;
identify forgotten or unmanaged cloud and development assets;
verify backup integrity and recovery procedures;
conduct risk-based vulnerability assessments and penetration testing;
define incident escalation and response responsibilities;
monitor remediated systems for evidence that compromise may have occurred before patching.
The key is to avoid waiting for definitive evidence of a breach before assessing exposure. When scanning and exploitation are automated, attackers may discover a vulnerable service before its owner realizes the service is still publicly reachable.

The cyberattack activity reported in Indonesia is another reminder that large-scale exploitation is increasingly automated.
Financial services and government systems are visible high-value targets, but automated attackers do not limit themselves to large organizations. Any publicly accessible server, application, VPN gateway, cloud workload or API with a usable weakness can become part of the attack surface.
Organizations should therefore move beyond asking: “Have we already been attacked?”. A more useful question is: “If attackers test our infrastructure today, do we know what is exposed, which weaknesses are exploitable, whether an intrusion would be detected and how quickly we could respond?”
For Indonesian organizations, answering that question requires more than deploying security products. It requires continuous visibility, vulnerability remediation, realistic validation through Pentest, effective monitoring and a response process that can turn security signals into action.
References














