Ross ROSS = Recommend OSS · open-source software intelligence for agents

zeustrojancode/Zeus

NOT MY CODE! Zeus trojan horse - leaked in 2011, I am not the author. This repository is for study purposes only, do not message me about your lame hacking attempts. observed · 2026-08-28

github.com/zeustrojancode/Zeus · homepage · C · archived observed · 2026-08-28

Health v2 · maintenance only

10/100

  • Activity 0
  • Release rhythm 35
  • Longevity 100

Flags: no_releases archived no_license

How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: n/a
  • age_days: 5591
  • days_rel: n/a
  • days_push: 2094
  • n_releases_24m: 0

Full methodology

Adoption not part of the score

1567 stars · 698 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

A GitHub mirror of the leaked source code (version 2.0.8.9) of the Zeus trojan, a notorious Windows banking malware from 2007-2011 that stole credentials via man-in-the-browser keystroke logging and form grabbing. The repository contains no original code from its uploader and exists solely so security researchers can download and study this historically significant malware sample, including its builder and bot configuration tooling.

Use cases

  • study the source code of the Zeus banking trojan
  • analyze a historical malware sample for security research
  • learn how man-in-the-browser keylogging and form grabbing worked
  • build defensive signatures and detection rules from real trojan source
  • research botnet architecture and C2 configuration formats
  • teach malware analysis with a famous leaked codebase

When to choose

  • You need the authentic leaked Zeus source for malware analysis, forensics, or security training
  • You are researching the history and internals of banking trojans and botnets
  • You want to derive IOCs or detection signatures from a real malware implementation

When to avoid

  • You intend to run, deploy, or repurpose the code - it is functional malware and doing so is illegal and unethical
  • You want maintained, licensed software - there is no license, no active development, and the code reflects 2011-era techniques
  • You need a modern security tool or defensive framework rather than a static research artifact

Facets

application · maturity abandoned

security security windows c cpp malware trojan botnet keylogger banking-trojan zbot leaked-source-code malware-analysis security-research reverse-engineering historical-sample desktop

3 sources

Member repositories

RepositoryRoleHealth v2
zeustrojancode/Zeusmain10

For agents

markdown · JSON · MCP: product_card(name="zeustrojancode/Zeus")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem