db --> 1593511930000

CODE-OF-CONDUCT.md

@@ -1,21 +1,21 @@
 # Code of Conduct
 
-This code of conduct outlines our expectations for participants within the [theZoo](https://www.github.com/ytisf/theZoo/) community, as well as steps to reporting unacceptable behavior. We are committed to providing a welcoming and inspiring community for all and expect our code of conduct to be honored. Anyone who violates this code of conduct may be banned from the community.
+This code of conduct outlines our expectations for participants within the [theZoo](https://www.github.com/ytisf/theZoo/) community, as well as steps to reporting unacceptable behaviour. We are committed to providing a welcoming and inspiring community for all and expect our code of conduct to be honoured. Anyone who violates this code of conduct may be banned from the community.
 
 Our open source community strives to:
 
 * **Be friendly and patient.**
 * **Be welcoming**: We strive to be a community that welcomes and supports people of all backgrounds and identities. This includes, but is not limited to members of any race, ethnicity, culture, national origin, colour, immigration status, social and economic class, educational level, sex, sexual orientation, gender identity and expression, age, size, family status, political belief, religion, and mental and physical ability.
 * **Be considerate**: Your work will be used by other people, and you in turn will depend on the work of others. Any decision you take will affect users and colleagues, and you should take those consequences into account when making decisions. Remember that we're a world-wide community, so you might not be communicating in someone else's primary language.
-* **Be respectful**:  Not all of us will agree all the time, but disagreement is no excuse for poor behavior and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It’s important to remember that a community where people feel uncomfortable or threatened is not a productive one.
+* **Be respectful**:  Not all of us will agree all the time, but disagreement is no excuse for poor behaviour and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It’s important to remember that a community where people feel uncomfortable or threatened is not a productive one.
-* **Be careful in the words that you choose**: we are a community of professionals, and we conduct ourselves professionally. Be kind to others. Do not insult or put down other participants. Harassment and other exclusionary behavior aren't acceptable. This includes, but is not limited to:
+* **Be careful in the words that you choose**: we are a community of professionals, and we conduct ourselves professionally. Be kind to others. Do not insult or put down other participants. Harassment and other exclusionary behaviour aren't acceptable. This includes, but is not limited to:
   * Violent threats or language directed against another person.
   * Discriminatory jokes and language.
   * Posting sexually explicit or violent material.
   * Posting (or threatening to post) other people's personally identifying information ("doxing").
   * Personal insults, especially those using racist or sexist terms.
   * Unwelcome sexual attention.
-  * Advocating for, or encouraging, any of the above behavior.
+  * Advocating for, or encouraging, any of the above behaviour.
   * Repeated harassment of others. In general, if someone asks you to stop, then stop.
 * **When we disagree, try to understand why**: Disagreements, both social and technical, happen all the time. It is important that we resolve disagreements and differing views constructively. Remember that we’re different. The strength of our community comes from its diversity, people from a wide range of backgrounds. Different people have different perspectives on issues. Being unable to understand why someone holds a viewpoint doesn’t mean that they’re wrong. Don’t forget that it is human to err and blaming each other doesn’t get us anywhere. Instead, focus on helping to resolve issues and learning from mistakes.
 
@@ -25,10 +25,10 @@ This code is not exhaustive or complete. It serves to distill our common underst
 
 We encourage everyone to participate and are committed to building a community for all. Although we may not be able to satisfy everyone, we all agree that everyone is equal. Whenever a participant has made a mistake, we expect them to take responsibility for it. If someone has been harmed or offended, it is our responsibility to listen carefully and respectfully, and do our best to right the wrong.
 
-Although this list cannot be exhaustive, we explicitly honor diversity in age, gender, gender identity or expression, culture, ethnicity, language, national origin, political beliefs, profession, race, religion, sexual orientation, socioeconomic status, and technical ability. We will not tolerate discrimination based on any of the protected
+Although this list cannot be exhaustive, we explicitly honour diversity in age, gender, gender identity or expression, culture, ethnicity, language, national origin, political beliefs, profession, race, religion, sexual orientation, socioeconomic status, and technical ability. We will not tolerate discrimination based on any of the protected
 characteristics above, including participants with disabilities.
 
-### Unacceptable Behavior
+### Unacceptable Behaviour
 
 Harassment may include but not limited to the following:
 
@@ -43,14 +43,14 @@ Harassment may include but not limited to the following:
 
 ### Reporting Issues
 
-If you experience or witness unacceptable behavior—or have any other concerns—please report it by contacting us via [this email address](mailto:thezoo+codeofconduct@morirt.com). All reports will be handled with discretion. 
+If you experience or witness unacceptable behaviour—or have any other concerns—please report it by contacting us via [this email address](mailto:thezoo+codeofconduct@morirt.com). All reports will be handled with discretion.
 
-Anyone asked to stop unacceptable behavior is expected to comply immediately. If an individual engages in unacceptable behavior, the representative may take any action they deem appropriate, up to and including a permanent ban from our community without warning.
+Anyone asked to stop unacceptable behaviour is expected to comply immediately. If an individual engages in unacceptable behaviour the representative may take any action they deem appropriate, up to and including a permanent ban from our community without warning.
 
 ## Thanks
 
-This code of conduct is based on the [Open Code of Conduct](https://github.com/todogroup/opencodeofconduct) from the [TODOGroup](http://todogroup.org). 
+This code of conduct is based on the [Open Code of Conduct](https://github.com/todogroup/opencodeofconduct) from the [TODOGroup](http://todogroup.org).
 
 Portions derived from the [Slack Developer Community Code of Conduct](https://api.slack.com/docs/community-code-of-conduct), [The Ada Initiative](https://adainitiative.org/2014/02/18/howto-design-a-code-of-conduct-for-your-community/), [geekfeminism.org](https://geekfeminism.org/about/code-of-conduct/)  and [Docker Code of Conduct](https://raw.githubusercontent.com/docker/code-of-conduct/master/code-of-conduct-EN.md).
 
-We are thankful for their work and all the communities who have paved the way with code of conducts.
+We are thankful for their work and all the communities who have paved the way with code of conducts.

CONTRIBUTING.md

@@ -6,22 +6,24 @@ The following is a set of guidelines as how to contribute, be it by Pull request
 
 ## Contribution
 ### Reporting Bugs
-Before creating bug reports please check the `bugs` section on GitHub. It might already be there... When you are creating a bug report, please include as many details as possible. General bug openings with 'this does not work' are probably just going to be closed as they are impossible to triage. 
+Before creating bug reports please check the `bugs` section on GitHub. It might already be there... When you are creating a bug report, please include as many details as possible. General bug openings with 'this does not work' are probably just going to be closed as they are impossible to triage.
 
 Explain the problem and include additional details to help maintainers reproduce the problem:
- 
+
 * Use a clear and descriptive title for the issue to identify the problem.
 * Describe the exact steps which reproduce the problem in as many details as possible.
 * Include system information (Python version, OS version, etc.).
-* Explain which behavior you expected to see instead and why.
+* Explain which behaviour you expected to see instead and why.
+
+**DO NOT** open bugs for malware not executing unless you are confident that the file itself is broken. Some malware won't run in virtualisation, some have anti debugging and some are DLLs. We can always recommend more information on the topic such as [this wonderful book](https://www.amazon.com/Practical-Malware-Analysis-Hands-Dissecting). But `theZoo`'s bug tracking system is not a support channel.   
+
+### Requesting Samples
+If a particular sample is of interest to you and it cannot be find the `theZoo` kindly [send an email to](mailto:thezoo+codeofconduct@morirt.com). Please do **not** open up an bug/feature request for a sample. We will attempt to upload that sample in the next batch.
 
-**DO NOT** open bugs for malware not executing unless you are confident that the file itself is broken. Some malware won't run in virtualization, some have anti debugging and some are DLLs. We can always recommend more information on the topic such as [this wonderful book](https://www.amazon.com/Practical-Malware-Analysis-Hands-Dissecting). But `theZoo`'s bug tracking system is not a support channel.   
- 
 ### Database Contributions
-Please see `prep_file.py` to assist you in creating the directory you need. However, this will not fill out the database. You can use any of the SQLite3 editors out there to add it to the database [`conf/maldb.db`]. Make sure you are accurate about your description, tags and info. The reliability and accuracy of the database is the main purpose for the existence of `theZoo`. Without a credible database this is just another malware dump. 
+Please see `prep_file.py` to assist you in creating the directory you need. However, this will not fill out the database. You can use any of the SQLite3 editors out there to add it to the database [`conf/maldb.db`]. Make sure you are accurate about your description, tags and info. The reliability and accuracy of the database is the main purpose for the existence of `theZoo`. Without a credible database this is just another malware dump.
 
 Edit the database and remember that file paths are case sensitive.  
 
 ### Suggesting Enhancements
-Similar to **Reporting Bugs** section. Please be descriptive. What exactly it is that you would like and what is the workflow you are seeing. The more descriptive you are the more likely it is for others in the community to vote for this and we will know to prioritize it.
+Similar to **Reporting Bugs** section. Please be descriptive. What exactly it is that you would like and what is the workflow you are seeing. The more descriptive you are the more likely it is for others in the community to vote for this and we will know to prioritise it.
- 

conf/db.ver

@@ -1 +1 @@
-1578844430000
+1593511930000

malwares/Binaries/Win32.StrongPity/Win32.StrongPity.md5

@@ -0,0 +1 @@
+645a5380540b135ad0d839b2f7366df7

malwares/Binaries/Win32.StrongPity/Win32.StrongPity.pass

@@ -0,0 +1 @@
+infected

malwares/Binaries/Win32.StrongPity/Win32.StrongPity.shasum

@@ -0,0 +1 @@
+ea4cf694b99f37cef961bf8daf936b56e5721b09610aa466676b0f8625c50161

malwares/Binaries/Win64.NukeSped/Win64.NukeSped.md5

@@ -0,0 +1 @@
+c92ac2a5a2c6d2b1826a0bbc1a56b01a

malwares/Binaries/Win64.NukeSped/Win64.NukeSped.pass

@@ -0,0 +1 @@
+infected

malwares/Binaries/Win64.NukeSped/Win64.NukeSped.shasum

@@ -0,0 +1 @@
+931f062a629950ad6fb85b83262cc3f730a6e94d43a27b48f7fd857f7722c6ba