MMD-071-2026 Linux/KinsingBot a "bad-bad" designed botnet
Comments on “MMD-071-2026 Linux/KinsingBot a "bad-bad" designed botnet”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
MalwareMustDie published a reverse-engineering report on Linux/Kinsing, a Go bot used by the SystemTen gang to deploy a modified XMRig miner. The analysis covers a 16 MB stripped Go 1.13 binary, mapping its commands to functions for Redis brute-forcing, SOCKS proxying, a backdoor and self-update. C2 traffic exposes clear-text victim headers, and the RSA key is embedded in the binary, giving defenders detection points. The 2019–2020 infrastructure is dead, but the family was active in 2024 and 2025. Binary and version-comparison details lack cited sources.
Why it ranked
No. 17 of 123 with a score of 0.67. The panel rated it highest on technical depth (0.94) and new information (0.91), lowest on audience breadth (0.57). Placed No. 17, No. 14 by score alone: the fifth Security story of the day (−0.040). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Detailed reverse-engineering of a Linux botnet (Kinsing) with concrete IOCs, C2 protocol and spreading mechanics; highly relevant to security-minded builders, though long, dated, and partly reposted from older material.}
- AI judgeJudge 3gpt-5.6-luna
- Detailed malware reverse engineering, dynamic traces, C2 protocol analysis, IOCs, and defensive guidance make this highly actionable for Linux defenders. Its main limitation is that the central case is historical, though the techniques remain relevant.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.67total under rubric v2.3
- Significance0.60
- Reader interest0.73
- Audience breadth0.57
- Practical relevance0.74
- Substantiated0.85
- Technical depth0.94
- New information0.91
- Counts against: Promotional0.02
- Counts against: Overclaim0.28
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.59 | 0.55 | 0.66 | 0.60 | 0.11 | +0.24 | +0.144 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.62 | 0.70 | 0.87 | 0.73 | 0.25 | +0.26 | +0.190 |
| Audience breadthHow many people who build technology does it concern? | 0.63 | 0.50 | 0.58 | 0.57 | 0.13 | +0.13 | +0.074 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.64 | 0.75 | 0.82 | 0.74 | 0.18 | +0.22 | +0.162 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.90 | 0.80 | 0.86 | 0.85 | 0.10 | +0.05 | +0.043 |
| Technical depthHow technically substantive is it? | 0.99 | 0.90 | 0.93 | 0.94 | 0.10 | +0.05 | +0.047 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.92 | 0.85 | 0.96 | 0.91 | 0.11 | +0.05 | +0.046 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.04 | 0.02 | 0.01 | 0.02 | 0.03 | −0.19 | −0.004 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.47 | 0.20 | 0.18 | 0.28 | 0.29 | −0.11 | −0.031 |
| Sum of contributions | +0.670 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.670 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-14/17/"><img src="https://rubric.hrih.si/badge/2026-11-14/17.svg" alt="Ranked #17 on Rubric, 14 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 3 matches source · 5 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Matches sourceDate
Kinsing (H2Miner) kept evolving after this analysis, including targeting Apache Tomcat servers in 2024.
The cited source says the same thing.
The article says “for example targeting Apache Tomcat servers in 2024 (Tenable”
The source says “Recently, we discovered that Kinsing also attacks Apache Tomcat servers, and uses new techniques to hide itself on the filesystem”
Source cited by the article: tenable.com/blog/kinsing-malware-hides-itself-as-a-manual-page-and-targets-cloud-servers
Matches sourceDate
Kinsing ran campaigns against companies in Russia in 2025.
The cited source says the same thing.
The article says “running campaigns against companies in Russia in 2025 (F6 on Habr”
The source says “Во втором квартале 2025 года департамент киберразведки (Threat Intelligence) компании F6 зафиксировал волну атак группировки Kinsing на российские компании из сфер финансов, логистики и телекома”
Source cited by the article: habr.com/ru/articles/935988
No source givenNumber
The analysed Kinsing sample is a 16.28 MB (17072128 bytes) statically compiled, stripped Go 1.13 ELF for x86-64.
The article gives no link or citation for it.
The article says “Size 16.28 MB (17072128 bytes”
The source says No source to compare with.
No source givenNumber
The Kinsing bot's hardcoded C2 list contains five addresses contacted over plain HTTP on tcp/80, including 45.10.88.102 and 91.215.169.111.
The article gives no link or citation for it.
The article says “The bot simply tries the C2s one by one over plain HTTP on tcp/80”
The source says No source to compare with.
No source givenVersion
The embedded miner is XMRig 5.5.0, built on Dec 29 2019.
The article gives no link or citation for it.
The article says “XMRig 5.5.0\n built on Dec 29 2019 with GCC”
The source says No source to compare with.
No source givenVersion
The v31 bot changed its initial C2 call path (s to ms, g to mg), uses a single hex-encoded C2 address, and removed the author name from config.
The article gives no link or citation for it.
The article says “Initial C2 call path is changed (s => ms, g => mg”
The source says No source to compare with.
No source givenCausal conclusion
The RSA private key in Kinsing v31 is byte-for-byte identical to the one recovered from v28, so the operator never rotated the C2 key.
The article gives no link or citation for it.
The article says “the RSA key in v31 is byte-for-byte identical to the key recovered from v28”
The source says No source to compare with.
Matches sourceGeneralization
The wallet in the build a71ad3 miner configuration is the one public researchers used to tie together the Docker, Redis and SaltStack waves of this family.
The cited source says the same thing.
The article says “This wallet is the one public researchers used to tie the Docker, Redis and SaltStack waves of this family together”
The source says “This wallet address appeared in miner samples from the Docker host, Redis, and SaltStack compromises”
Source cited by the article: zscaler.com/blogs/cybersecurity-best-practices/kinsing-malware-citrix-saltstack
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 2 pts, not on front page
Recorded for context only, checked 15 Nov 2026, 20:44 UTC. It played no part in the ranking.