theZoo – A repository of LIVE malwares for your own joy and pleasure

CERT-LatestNews ThreatsStrategic

theZoo is a project created to make the possibility of malware analysis open and available to the public. Since we have found out that almost all versions of malware are very hard to come by in a way which will allow analysis, we have decided to gather all of them for you in an accessible and safe way. theZoo was born by Yuval tisf Nativ and is now maintained by Shahak Shalev.

Documentation and Notes

theZoo’s objective is to offer a fast and easy way of retrieving malware samples and source code in an organized fashion in hopes of promoting malware research.

Root Files:
Since version 0.42 theZoo has been undergoing dramatic changes. It now runs in both CLI and ARGVS modes. You can call the program with the same command line arguments as before. The current default state of theZoo runtime is the CLI. The following files and directories are responsible for the application’s behaviour.

The conf folder holds files relevant to the particular running of the program but are not part of the application. You can find the EULA file in the conf and more.

Contains .py and .pyc import files used by the rest of the application

The actual malwares samples – be careful!

Malware source code 🙂

Directory Structure:
Each directory is composed of 4 files:

  • Malware files in an encrypted ZIP archive.
  • SHA256 sum of the 1st file.
  • MD5 sum of the 1st file.
  • Password file for the archive.

Structure of maldb.db
maldb.db is the DB which theZoo is acting upon to find malware indexed on your drive. The structure is as follows:

  • UID – Determined based on the indexing process.
  • Location – The location on the drive of the malware you have searched for.
  • Type – Sorts the different types of malware there are. So far we sort by: Virus, Trojans, Botnets, Ransomware, Spyware
  • Name – Just the name of the malware.
  • Version – Nothing to say here as well.
  • Author – … I’m not that into documentation…
  • Programming Language – The state of the malware in regard to source, bin, or which type of source. c/cpp/bin…
  • Date – See ‘Author’ section.
  • Architecture – The arch the platform was build for. Can be x86, x64, arm7….
  • Platform – Win32, Win64, *nix32, *nix64, iOS, android and so on.
  • Comments – Any comments there may be about the item.
  • Tags – Tags matching the item.

An example line will look as follow:


Bugs and Reports

Change Log for v0.60:

Change Log for v0.50:

Change Log for v0.42:

Change Log for v0.43:

Change Log for v0.50:

Predicted Change Log for v1.0