Researchers Track Suspected Kimsuky Infrastructure Using “Million OK!!!!” Response and Naver Branding

· Original article ↗

Summary

Hunt researchers linked newly observed domains and servers returning “Million OK!!!!” and displaying Naver branding to suspected Kimsuky infrastructure, identifying recurring domains, certificates, hosting, and server traits.

Key points

  • Recently registered domains and IPs returned the distinctive “Million OK!!!!” HTTP response, a marker researchers say may help identify active servers.
  • Some pages used Naver’s favicon; one domain appeared designed to mimic a Naver sign-in page.
  • Observed infrastructure reused domains under TLDs including p-e.kr, o-r.kr, and n-e.kr, previously associated with Kimsuky activity.
  • The observed IPs were hosted on the UCLOUD Information Technology ASN; several used Sectigo-issued TLS certificates.
  • Many servers shared an outdated Apache, OpenSSL, and PHP stack.
  • A separate server returning “Hello” shared infrastructure patterns and a certificate domain associated with an email previously linked by Unit 42 to KLogEXE and FPSpy domains.

Article Details

Attack Vectors
  • Naver-themed phishing pages use Naver branding and counterfeit sign-in pages to steal credentials; the article describes this as a recurring Kimsuky targeting pattern.
  • Observed infrastructure returned the distinctive HTTP response “Million OK!!!!”; the article says it may be used as a marker to verify active servers, but its purpose is unclear.
Defensive Notes
  • Monitor for the distinctive “Million OK!!!!” HTTP response, associated domains and IP addresses, Naver-themed pages, and the listed certificate fingerprints.
  • The observed infrastructure commonly used Apache/2.4.25 (Win32), OpenSSL/1.0.2j, and PHP/5.6.30; the article reports these as outdated server software.
  • HuntSQL Explorer was used to search scan results for the distinctive HTTP response.

Indicators of compromise

TypeIndicatorContext
DOMAINozszg[.]topHistorical domain resolving to an observed suspicious infrastructure IP.
EMAILcfa4a551515dc742s@gmail[.]comRegistrant email found for edoc-send.n-e[.]kr; Unit 42 reportedly linked it to two domains used by malware families.
HOSTNAMEedoc-send[.]n-e[.]krCertificate common name associated with the observed server and described as connected to phishing and C2 infrastructure patterns.
HOSTNAMEmail[.]ozszg[.]topHistorical hostname resolving to an observed suspicious infrastructure IP.
HOSTNAMEnidauth[.]r-e[.]krObserved domain presenting the Million OK response and Naver favicon; described as likely mimicking Naver sign-in.
HOSTNAMEnld[.]blog-view[.]o-r[.]krHistorical hostname resolving to an observed suspicious infrastructure IP.
IPV4101[.]36[.]114[.]153Observed server displaying a Naver favicon and a Hello response, linked by the article to the identified infrastructure patterns.
IPV4118[.]193[.]68[.]146Observed suspicious infrastructure returning the Million OK response.
IPV4118[.]193[.]69[.]248Historical IP associated with suspicious infrastructure and the listed domains.
IPV4118[.]194[.]248[.]148Observed suspicious infrastructure returning the Million OK response.
IPV4123[.]58[.]200[.]13Historical IP associated with the reported infrastructure.
IPV4123[.]58[.]200[.]50Observed suspicious infrastructure returning the Million OK response.
IPV4152[.]32[.]138[.]191Observed suspicious infrastructure returning the Million OK response.
IPV4152[.]32[.]138[.]63Historical IP associated with the reported infrastructure.
IPV4152[.]32[.]243[.]153Observed suspicious infrastructure returning the Million OK response.
IPV4152[.]32[.]243[.]184Historical IP associated with the suspicious hostname listed in the article.
SHA256393cbd41f14b1c55bde92a32e10b5d65384e33a97c77f352bd90fdb8fd5d73aeCertificate hash listed for *.nidcheck.o-r[.]kr.
SHA2565f2c65e695d85395634e7ab561242425e6ef281ce2e14a0d5c1704ed593cfa5fCertificate hash listed for *.againcheck[.]site.
SHA256974e386f8facff325ec2f3ebb7439a9a1e4e4c88944d5beb5c341923dc993556Certificate hash listed for *.checkagain[.]store.
SHA25698c85ef91e05593cd470ffe8698aa6d97b36e8b885200be87080b8c2a135fb9cCertificate hash listed for *.checkmail.kro[.]kr.
SHA256d8a8ddda6cc12c5533268b20e48e1b636ce9173e9f9b5bb4c832fe00f1b26841Certificate hash listed for *.nidcorp[.]store.

Threat Actors

Malware

Vendors

Products

Tools

Countries

Related Articles