{"id":5282,"date":"2026-10-15T07:12:44","date_gmt":"2026-10-15T07:12:44","guid":{"rendered":"https:\/\/cyberasia.io\/?p=5282"},"modified":"2026-10-15T07:12:47","modified_gmt":"2026-10-15T07:12:47","slug":"rippersec-ddos-hits-max-co-il","status":"publish","type":"post","link":"https:\/\/cyberasia.io\/article\/ddos\/rippersec-ddos-hits-max-co-il\/","title":{"rendered":"RipperSec DDoS Hits Max.co.il: Critical 0\/56 Node Report"},"content":{"rendered":"\n

The latest RipperSec<\/mark><\/strong> DDoS campaign pushed the public website of Israeli card issuer MAX IT Finance Ltd<\/mark><\/strong> into error pages on Monday, September 14, 2026. Max, formerly known as Leumi Card, appeared on the group’s #OpZionistV2<\/mark><\/strong> target list with a start time of 15:00. Screenshots posted by the group show 429 Too Many Requests errors, a fallback notice hosted on a googleapis.com address, and public check-host reports where most probe locations failed to load www.max.co.il.<\/p>\n\n\n\n

Max has not published an incident statement in any material seen by CyberAsia, so the real customer impact is not known. The screenshots show a familiar routine: announce a target, run a flood, then circulate probe results as public proof.<\/p>\n\n\n\n

\"Figure
Figure 1 : RipperSec DDoS target announcement for MAX IT Finance Ltd under #OpZionistV2, dated 14\/09\/2026<\/figcaption><\/figure>\n\n\n\n

RipperSec DDoS Timeline: How the Max.co.il Attack Unfolded<\/h2>\n\n\n\n

The announcement carries a 14:01 timestamp, with banner artwork branded #OpZionist V2 and a header reading NEW TARGET RELEASED. It lists MAX IT Finance Ltd as the target and describes it as one of Israel’s leading credit card companies<\/mark><\/strong>. The order time was 15:00 on 14\/09\/2026, with the time zone field reading 08:00 GMT.<\/p>\n\n\n\n

A second post served as the technical brief. It named www.max.co.il, listed four IP addresses, gave ports 80 and 443, and identified Amazon as the hosting provider. CyberAsia has withheld the addresses, the message field and the names of forwarding sources.<\/p>\n\n\n\n

More posts followed through the afternoon. At 15:18 the group shared two browser screenshots and a check-host.net report. More check-host material appeared at 15:30 and between 15:44 and 15:53, alongside a FREE PALESTINE message. The last posts, at 16:34 and 16:36, circled an Israeli probe location and added the words Good job, soldier. View counts stayed between 18 and 52, so the audience looked small.<\/p>\n\n\n\n

Who Is RipperSec and What Is #OpZionistV2?<\/h2>\n\n\n\n

Public threat intelligence profiles describe RipperSec as a pro-Palestinian hacktivist group and emerged in June 2023. Cyble’s profile<\/mark><\/a><\/strong> credits it with close to 200 DDoS attacks, many aimed at Israeli government and private sector websites. Radware has separately written about MegaMedusa<\/mark><\/a><\/strong>, a public web DDoS tool linked to the group. The screenshots here do not name the tool used against Max.<\/p>\n\n\n\n

The V2 in #OpZionistV2 suggests a second round of an earlier operation, though this material does not show the first.<\/p>\n\n\n\n

https:\/\/cyberasia.io\/actor\/rippersec\/<\/mark><\/a><\/strong>: CyberAsia.io coverage of earlier RipperSec DDoS operations.<\/p>\n\n\n\n

\"Figure
Figure 2 : RipperSec DDoS group logo with a skull, crescent moons and Arabic script<\/figcaption><\/figure>\n\n\n\n

What the Screenshots Show About the Max.co.il Outage<\/h2>\n\n\n\n

The 429 page, the fallback notice and the first report<\/mark><\/strong><\/p>\n\n\n\n

Figure 3 combines two browser captures. The first sits on a googleapis.com address and says the site cannot display information right now, then lists urgent options for visitors abroad: a voice line for a secret code, a 24\/7 contact for lost or stolen cards, and WhatsApp. The second shows max.co.il<\/mark><\/a><\/strong> returning 429 Too Many Requests, with a RipperSec logo laid over the page. That overlay is the group’s own branding, so the image works as publicity material and not as an independent log.<\/p>\n\n\n\n

A 429 is a rate limiting response, which usually means a protective layer is throttling traffic. It is not the same as a collapsed server. The check-host.net report in the same post is mixed. Finland and Germany returned 200 OK after roughly 13 to 25 seconds, Hong Kong returned 502 Bad Gateway, both Jakarta probes got 303 redirects in about 1.3 seconds, and Iranian probes failed with timeouts, refusals and a reset connection.<\/p>\n\n\n\n

\"Figure
Figure 3 : RipperSec DDoS screenshots of a Max.co.il fallback notice, a 429 page and a check-host.net report<\/figcaption><\/figure>\n\n\n\n

The 0 of 56 result and the 403 detail<\/mark><\/strong><\/p>\n\n\n\n

The check-host.cc<\/mark><\/strong> map in Figure 4 is the strongest visual. Dated September 14, 2026, it shows HTTP 0\/56 nodes up, with most continents in red. A bot output forwarded with a GOJO label lists the target as DOWN with a 403 code, plus 3 successful checks, 27 failures and 9 blocked. A 403 is a refusal, not a timeout, so it can mean an edge filter was rejecting automated probes. Another check in the same screenshot shows 200 responses taking about 13 to 17 seconds, which describes a degraded site, not a dead one.<\/p>\n\n\n\n

\"Figure
Figure 4 : RipperSec DDoS check-host.cc map showing 0 of 56 nodes up for www.max.co.il<\/figcaption><\/figure>\n\n\n\n

Netanya, Sydney and the limits of probe data<\/mark><\/strong><\/p>\n\n\n\n

Figure 5 shows a check-host table where the group circled Israel, Netanya as Connection timed out. The line just below, Tel Aviv, still reads OK. The second report shows a mostly red map, a Tirana probe ending in ERR_CANCELED<\/strong>, and a Sydney probe with a 502 and 0 of 24<\/mark><\/strong> successful checks.<\/p>\n\n\n\n

Taken together, the evidence supports degraded or restricted access from many locations on the afternoon of September 14. It does not show a full shutdown of card services, the mobile app or payment processing. Some Israeli sites also limit foreign traffic, so certain country-level failures may predate the attack.<\/p>\n\n\n\n

\"Figure
Figure 5 : RipperSec DDoS check-host table circling a Netanya timeout beside a Sydney 502 report<\/figcaption><\/figure>\n\n\n\n

Defense Notes for Financial Sites Facing a RipperSec DDoS<\/h2>\n\n\n\n

Layer 7 floods aimed at ports 80 and 443 are best absorbed before traffic reaches the origin. Teams at card issuers and banks can take four steps:<\/p>\n\n\n\n

    \n
  • Put a CDN or scrubbing service in front of every public hostname, with rate limits and bot challenges.<\/li>\n\n\n\n
  • Host a fallback notice and status page on separate infrastructure.<\/li>\n\n\n\n
  • Split the marketing site from login, app APIs and payment endpoints.<\/li>\n\n\n\n
  • Monitor from several regions and compare 429, 502 and 403 patterns before calling an outage.<\/li>\n<\/ul>\n\n\n\n

    FAQ<\/h2>\n\n\n\n

    Q1 : Was customer card data stolen in the Max.co.il attack?<\/mark><\/strong><\/p>\n\n\n\n

    Nothing in the screenshots points to data theft. A DDoS floods a site with requests and does not by itself expose records. Customers should still distrust unexpected texts or emails about card problems, since scammers often use outage news as cover.<\/p>\n\n\n\n

    Q2 : Was Max.co.il really offline everywhere?<\/mark><\/strong><\/p>\n\n\n\n

    The evidence says no. One report shows 0 of 56 nodes up, yet other probes returned 200 and 303 responses, and Tel Aviv read OK in the circled table. Slow pages, rate limiting and filtered probes can all look like downtime on a public checker.<\/p>\n\n\n\n

    Q3 : What should an IT admin do first during a flood like this?<\/mark><\/strong><\/p>\n\n\n\n

    Contact the CDN or hosting provider, switch on rate limiting and challenge rules for the targeted paths, and keep full request logs. Then publish a plain status message so customers know which services still work.<\/p>\n\n\n\n

    Research Notice<\/h2>\n\n\n\n

    This article is published for cybersecurity research and educational purposes only. CyberAsia.io does not endorse or encourage any cyberattack or unlawful activity. The information comes from screenshots and public posts, and sensitive details such as IP addresses have been withheld. Readers must not attempt to access, test or disrupt any system named here.<\/p>\n\n\n\n

    <\/p>\n","protected":false},"excerpt":{"rendered":"

    The latest RipperSec DDoS campaign pushed the public website of Israeli card issuer MAX IT Finance Ltd into error pages on Monday, September 14, 2026. Max, formerly known as Leumi Card, appeared on the group’s #OpZionistV2 target list with a start time of 15:00. Screenshots posted by the group show 429 Too Many Requests errors, […]<\/p>\n","protected":false},"author":3,"featured_media":5283,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[1656,2627,1184,2385,1188,14,1923,2760,21,2318,1664,2758,2757,2759,603,1282,1286,24,2700,1649,2381,1256,2651,2007,2072,1263,2067,1245,1395,1160],"threat_actors":[409],"class_list":["post-5282","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ddos","tag-berita-keamanan-siber","tag-check-host-2","tag-ciberseguridad","tag-cyber-security-news","tag-cybersecurite","tag-ddos-attack","tag-ddos-","tag-hacktivist","tag-israel-cyber-attack","tag-keselamatan-siber","tag-leumi-card","tag-max-it-finance","tag-max-co-il","tag-opzionistv2","tag-penggodam","tag-peretas","tag-rippersec","tag-rippersec-ddos","tag-serangan-ddos","tag-siber-guvenlik","tag-1256","tag-2651","tag-2007","tag-2072","tag-1263","tag-2067","tag-1245","tag-1395","tag-1160","threat_actor-rippersec"],"_links":{"self":[{"href":"https:\/\/cyberasia.io\/people\/wp-json\/wp\/v2\/posts\/5282","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cyberasia.io\/people\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cyberasia.io\/people\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cyberasia.io\/people\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/cyberasia.io\/people\/wp-json\/wp\/v2\/comments?post=5282"}],"version-history":[{"count":3,"href":"https:\/\/cyberasia.io\/people\/wp-json\/wp\/v2\/posts\/5282\/revisions"}],"predecessor-version":[{"id":5292,"href":"https:\/\/cyberasia.io\/people\/wp-json\/wp\/v2\/posts\/5282\/revisions\/5292"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cyberasia.io\/people\/wp-json\/wp\/v2\/media\/5283"}],"wp:attachment":[{"href":"https:\/\/cyberasia.io\/people\/wp-json\/wp\/v2\/media?parent=5282"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cyberasia.io\/people\/wp-json\/wp\/v2\/categories?post=5282"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cyberasia.io\/people\/wp-json\/wp\/v2\/tags?post=5282"},{"taxonomy":"threat_actor","embeddable":true,"href":"https:\/\/cyberasia.io\/people\/wp-json\/wp\/v2\/threat_actors?post=5282"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}