/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Report: the number of malware strains written in Go have increased by around 2,000% since 2017, after APTs and cybercrime groups adopted the language

ZDNet Catalin Cimpanu

Context & Ripple Effects

The Go surge sits between two data points in the corpus: developers had already flagged Go as a language they wanted to learn — a HackerEarth survey put it ahead of Python months before this report — so threat actors were adopting a toolchain with a growing talent pool and rich standard library. Months later, researchers confirmed the motivation explicitly: malware writers use Go and other 'exotic' languages specifically to hamper analysis and evade detection.

First-order effects

  • Antivirus engines and sandbox tools tuned for C-family binaries now face Go's bulky, runtime-embedded executables, forcing security vendors to rebuild detection signatures and analyst tooling around a new compiler output.

Second-order effects

  • Go's native cross-compilation lets one codebase target Windows and Linux alike, feeding the broader run of malware aimed at Linux-based IoT systems that CrowdStrike measured rising 35% year over year in 2021.

Third-order effects

  • As language choice becomes an evasion tactic rather than an engineering preference, defenders are pushed toward behavior-based detection — a shift consistent with CrowdStrike's later finding that most intrusions are now malware-free, which suggests the arms race fragments into compiled-malware evasion on one side and credential-based attacks that skip binaries entirely on the other.

The trend: Malware development is industrializing around mainstream, developer-friendly languages like Go, turning compiler choice itself into a defense-evasion technique.

Discussion

  • @accidentalrebel Karlo Licudine on x
    “...Go-based binaries are still hard to analyze and reverse engineer... which has kept detection rates for Go-based malware very low.” Thoughts @malwrhunterteam and @c3rb3ru5d3d53c? I haven't encountered a Go malware in my studies yet so I'm curious. https://www.zdnet.com/...
  • @jboursiquot Johnny Boursiquot on x
    Interesting use case for #golang that I never thought about. Go malware is now common, having been adopted by both APTs and e-crime groups | ZDNet https://www.zdnet.com/... https://twitter.com/...
  • @campuscodi Catalin Cimpanu on x
    Go malware is now common, having been adopted by both APTs and e-crime groups From an Intezer report this week: “Before 2019, spotting malware written in Go was more a rare occurrence and during 2019 it became a daily occurrence.” https://www.zdnet.com/... https://twitter.com/...