Skip to content
NewA calmer, faster ZeroHour

SANS diary uses Kibana to hunt odd HTTP charsets in honeypot logs

Original title: Looking for a Language [Guest Diary], (Wed, Oct 21st)

SANS Internet Storm Center ()9 min read1
AI summary · x-ai/grok-4.7Summaries by Vani AI

A DShield honeypot logged about 960,000 events in three weeks, and Accept-Charset GBK stood out on SonicWall login probes.

An ISC guest diary walks through using Elastic Kibana Discover and Field Statistics on a SANS DShield honeypot index named cowrie. In a little more than three weeks the Raspberry Pi honeypot produced about 960,000 logs across only four rules, of which 15,271 records triggered a rule. The author narrows to the SonicWall Appliance Login Page rule, covering 41 hosts, then uses long-tail field distributions to spot an Accept-Charset preference for GBK over utf-8.

Unconfirmed: The diary treats the GBK charset preference as a lead, not confirmed attacker attribution.

Key facts
  • About 960,000 logs fell under only four detection rules.
  • Without filters, 15,271 records triggered a rule and 944,866 did not.
  • The SonicWall login-page rule matched 41 hosts.
  • The notable header preferred GBK, then utf-8, then a wildcard.
  • Other rules covered the index page, Git config scraping, and Fortinet emulation.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

Indicators of compromise

auto-extracted · verify before use · export allAll
TypeIndicatorContext
domainleheedu.cnet as extracted with this ESQL Query: source.domain values: leheedu[.]cn mail.,brossy.com[.]cn mail.brossy.com[.]cn tzrhxln[.]cn A
domaintzrhxln.cndiscovered an obviously automated campaign. Interestingly, tzrhxln[.]cn ( 165[.]154.29.93 ) is a suspect high entropy domain. Sim
ipv4165.154.11.140ame Canadian based AS-7456: 165[.]154.36.91 165[.]154.29.93 165[.]154.11.140 165[.]154.120.226 165[.]154.33.72 165[.]154.182.221 Value
ipv4165.154.120.226d AS-7456: 165[.]154.36.91 165[.]154.29.93 165[.]154.11.140 165[.]154.120.226 165[.]154.33.72 165[.]154.182.221 Values for http.request
ipv4165.154.182.22154.29.93 165[.]154.11.140 165[.]154.120.226 165[.]154.33.72 165[.]154.182.221 Values for http.request.body.content were all consistent
ipv4165.154.29.93s all from the same Canadian based AS-7456: 165[.]154.36.91 165[.]154.29.93 165[.]154.11.140 165[.]154.120.226 165[.]154.33.72 165[.]
ipv4165.154.33.7254.36.91 165[.]154.29.93 165[.]154.11.140 165[.]154.120.226 165[.]154.33.72 165[.]154.182.221 Values for http.request.body.content we
ipv4165.154.36.91set of endpoints all from the same Canadian based AS-7456: 165[.]154.36.91 165[.]154.29.93 165[.]154.11.140 165[.]154.120.226 165[.]

From the original article

9 min read at isc.sans.edu

[This is a Guest Diary by Jeffray Spence, an ISC intern as part of the SANS. edu BACS program]

SANS Internet Storm Center

isc.sans.edu

Read the full article at SANS Internet Storm Center

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.