├── LICENSE
├── README.md
├── code_assessment
└── puma_scan.md
├── cryptography
└── hashview.md
├── exploitation
├── avet.md
├── gef.md
├── mailsniper.md
└── rattler.md
├── forensics
├── inVtero.net.md
└── userline.md
├── frameworks
├── defplorex.md
├── dradis_framework.md
└── kubebot.md
├── hardening
└── lynis.md
├── hardware_iot
├── .keep
└── WHID.md
├── ics_scada
└── .keep
├── malware_research
├── .keep
├── ProcInfo.md
├── floss.md
└── sniffMK.md
├── mobile_hacking
├── androidtamer.md
├── badintent.md
├── kwetza.md
├── mobsf.md
└── needle.md
├── network_attacks
├── crowbar.md
├── delta.md
├── det.md
├── eaphammer.md
├── egression.md
├── flashlight.md
├── gr-lora.md
└── yasuo.md
├── network_defense
├── lulu.md
├── sitch.md
├── sweetsecurity.md
└── zenected.md
├── osint
├── .keep
└── datasploit.md
├── phishing
└── spf.md
├── red_team
├── legion.md
├── shinobot.md
└── warberrypi.md
├── reverse_engineering
└── .keep
├── tool_template.md
├── vulnerability_assessment
└── apt2.md
└── webapp_security
├── jack.md
├── owtf.md
├── wssat.md
└── zap.md
/LICENSE:
--------------------------------------------------------------------------------
1 | GNU GENERAL PUBLIC LICENSE
2 | Version 3, 29 June 2007
3 |
4 | Copyright (C) 2007 Free Software Foundation, Inc.
5 | Everyone is permitted to copy and distribute verbatim copies
6 | of this license document, but changing it is not allowed.
7 |
8 | Preamble
9 |
10 | The GNU General Public License is a free, copyleft license for
11 | software and other kinds of works.
12 |
13 | The licenses for most software and other practical works are designed
14 | to take away your freedom to share and change the works. By contrast,
15 | the GNU General Public License is intended to guarantee your freedom to
16 | share and change all versions of a program--to make sure it remains free
17 | software for all its users. We, the Free Software Foundation, use the
18 | GNU General Public License for most of our software; it applies also to
19 | any other work released this way by its authors. You can apply it to
20 | your programs, too.
21 |
22 | When we speak of free software, we are referring to freedom, not
23 | price. Our General Public Licenses are designed to make sure that you
24 | have the freedom to distribute copies of free software (and charge for
25 | them if you wish), that you receive source code or can get it if you
26 | want it, that you can change the software or use pieces of it in new
27 | free programs, and that you know you can do these things.
28 |
29 | To protect your rights, we need to prevent others from denying you
30 | these rights or asking you to surrender the rights. Therefore, you have
31 | certain responsibilities if you distribute copies of the software, or if
32 | you modify it: responsibilities to respect the freedom of others.
33 |
34 | For example, if you distribute copies of such a program, whether
35 | gratis or for a fee, you must pass on to the recipients the same
36 | freedoms that you received. You must make sure that they, too, receive
37 | or can get the source code. And you must show them these terms so they
38 | know their rights.
39 |
40 | Developers that use the GNU GPL protect your rights with two steps:
41 | (1) assert copyright on the software, and (2) offer you this License
42 | giving you legal permission to copy, distribute and/or modify it.
43 |
44 | For the developers' and authors' protection, the GPL clearly explains
45 | that there is no warranty for this free software. For both users' and
46 | authors' sake, the GPL requires that modified versions be marked as
47 | changed, so that their problems will not be attributed erroneously to
48 | authors of previous versions.
49 |
50 | Some devices are designed to deny users access to install or run
51 | modified versions of the software inside them, although the manufacturer
52 | can do so. This is fundamentally incompatible with the aim of
53 | protecting users' freedom to change the software. The systematic
54 | pattern of such abuse occurs in the area of products for individuals to
55 | use, which is precisely where it is most unacceptable. Therefore, we
56 | have designed this version of the GPL to prohibit the practice for those
57 | products. If such problems arise substantially in other domains, we
58 | stand ready to extend this provision to those domains in future versions
59 | of the GPL, as needed to protect the freedom of users.
60 |
61 | Finally, every program is threatened constantly by software patents.
62 | States should not allow patents to restrict development and use of
63 | software on general-purpose computers, but in those that do, we wish to
64 | avoid the special danger that patents applied to a free program could
65 | make it effectively proprietary. To prevent this, the GPL assures that
66 | patents cannot be used to render the program non-free.
67 |
68 | The precise terms and conditions for copying, distribution and
69 | modification follow.
70 |
71 | TERMS AND CONDITIONS
72 |
73 | 0. Definitions.
74 |
75 | "This License" refers to version 3 of the GNU General Public License.
76 |
77 | "Copyright" also means copyright-like laws that apply to other kinds of
78 | works, such as semiconductor masks.
79 |
80 | "The Program" refers to any copyrightable work licensed under this
81 | License. Each licensee is addressed as "you". "Licensees" and
82 | "recipients" may be individuals or organizations.
83 |
84 | To "modify" a work means to copy from or adapt all or part of the work
85 | in a fashion requiring copyright permission, other than the making of an
86 | exact copy. The resulting work is called a "modified version" of the
87 | earlier work or a work "based on" the earlier work.
88 |
89 | A "covered work" means either the unmodified Program or a work based
90 | on the Program.
91 |
92 | To "propagate" a work means to do anything with it that, without
93 | permission, would make you directly or secondarily liable for
94 | infringement under applicable copyright law, except executing it on a
95 | computer or modifying a private copy. Propagation includes copying,
96 | distribution (with or without modification), making available to the
97 | public, and in some countries other activities as well.
98 |
99 | To "convey" a work means any kind of propagation that enables other
100 | parties to make or receive copies. Mere interaction with a user through
101 | a computer network, with no transfer of a copy, is not conveying.
102 |
103 | An interactive user interface displays "Appropriate Legal Notices"
104 | to the extent that it includes a convenient and prominently visible
105 | feature that (1) displays an appropriate copyright notice, and (2)
106 | tells the user that there is no warranty for the work (except to the
107 | extent that warranties are provided), that licensees may convey the
108 | work under this License, and how to view a copy of this License. If
109 | the interface presents a list of user commands or options, such as a
110 | menu, a prominent item in the list meets this criterion.
111 |
112 | 1. Source Code.
113 |
114 | The "source code" for a work means the preferred form of the work
115 | for making modifications to it. "Object code" means any non-source
116 | form of a work.
117 |
118 | A "Standard Interface" means an interface that either is an official
119 | standard defined by a recognized standards body, or, in the case of
120 | interfaces specified for a particular programming language, one that
121 | is widely used among developers working in that language.
122 |
123 | The "System Libraries" of an executable work include anything, other
124 | than the work as a whole, that (a) is included in the normal form of
125 | packaging a Major Component, but which is not part of that Major
126 | Component, and (b) serves only to enable use of the work with that
127 | Major Component, or to implement a Standard Interface for which an
128 | implementation is available to the public in source code form. A
129 | "Major Component", in this context, means a major essential component
130 | (kernel, window system, and so on) of the specific operating system
131 | (if any) on which the executable work runs, or a compiler used to
132 | produce the work, or an object code interpreter used to run it.
133 |
134 | The "Corresponding Source" for a work in object code form means all
135 | the source code needed to generate, install, and (for an executable
136 | work) run the object code and to modify the work, including scripts to
137 | control those activities. However, it does not include the work's
138 | System Libraries, or general-purpose tools or generally available free
139 | programs which are used unmodified in performing those activities but
140 | which are not part of the work. For example, Corresponding Source
141 | includes interface definition files associated with source files for
142 | the work, and the source code for shared libraries and dynamically
143 | linked subprograms that the work is specifically designed to require,
144 | such as by intimate data communication or control flow between those
145 | subprograms and other parts of the work.
146 |
147 | The Corresponding Source need not include anything that users
148 | can regenerate automatically from other parts of the Corresponding
149 | Source.
150 |
151 | The Corresponding Source for a work in source code form is that
152 | same work.
153 |
154 | 2. Basic Permissions.
155 |
156 | All rights granted under this License are granted for the term of
157 | copyright on the Program, and are irrevocable provided the stated
158 | conditions are met. This License explicitly affirms your unlimited
159 | permission to run the unmodified Program. The output from running a
160 | covered work is covered by this License only if the output, given its
161 | content, constitutes a covered work. This License acknowledges your
162 | rights of fair use or other equivalent, as provided by copyright law.
163 |
164 | You may make, run and propagate covered works that you do not
165 | convey, without conditions so long as your license otherwise remains
166 | in force. You may convey covered works to others for the sole purpose
167 | of having them make modifications exclusively for you, or provide you
168 | with facilities for running those works, provided that you comply with
169 | the terms of this License in conveying all material for which you do
170 | not control copyright. Those thus making or running the covered works
171 | for you must do so exclusively on your behalf, under your direction
172 | and control, on terms that prohibit them from making any copies of
173 | your copyrighted material outside their relationship with you.
174 |
175 | Conveying under any other circumstances is permitted solely under
176 | the conditions stated below. Sublicensing is not allowed; section 10
177 | makes it unnecessary.
178 |
179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
180 |
181 | No covered work shall be deemed part of an effective technological
182 | measure under any applicable law fulfilling obligations under article
183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or
184 | similar laws prohibiting or restricting circumvention of such
185 | measures.
186 |
187 | When you convey a covered work, you waive any legal power to forbid
188 | circumvention of technological measures to the extent such circumvention
189 | is effected by exercising rights under this License with respect to
190 | the covered work, and you disclaim any intention to limit operation or
191 | modification of the work as a means of enforcing, against the work's
192 | users, your or third parties' legal rights to forbid circumvention of
193 | technological measures.
194 |
195 | 4. Conveying Verbatim Copies.
196 |
197 | You may convey verbatim copies of the Program's source code as you
198 | receive it, in any medium, provided that you conspicuously and
199 | appropriately publish on each copy an appropriate copyright notice;
200 | keep intact all notices stating that this License and any
201 | non-permissive terms added in accord with section 7 apply to the code;
202 | keep intact all notices of the absence of any warranty; and give all
203 | recipients a copy of this License along with the Program.
204 |
205 | You may charge any price or no price for each copy that you convey,
206 | and you may offer support or warranty protection for a fee.
207 |
208 | 5. Conveying Modified Source Versions.
209 |
210 | You may convey a work based on the Program, or the modifications to
211 | produce it from the Program, in the form of source code under the
212 | terms of section 4, provided that you also meet all of these conditions:
213 |
214 | a) The work must carry prominent notices stating that you modified
215 | it, and giving a relevant date.
216 |
217 | b) The work must carry prominent notices stating that it is
218 | released under this License and any conditions added under section
219 | 7. This requirement modifies the requirement in section 4 to
220 | "keep intact all notices".
221 |
222 | c) You must license the entire work, as a whole, under this
223 | License to anyone who comes into possession of a copy. This
224 | License will therefore apply, along with any applicable section 7
225 | additional terms, to the whole of the work, and all its parts,
226 | regardless of how they are packaged. This License gives no
227 | permission to license the work in any other way, but it does not
228 | invalidate such permission if you have separately received it.
229 |
230 | d) If the work has interactive user interfaces, each must display
231 | Appropriate Legal Notices; however, if the Program has interactive
232 | interfaces that do not display Appropriate Legal Notices, your
233 | work need not make them do so.
234 |
235 | A compilation of a covered work with other separate and independent
236 | works, which are not by their nature extensions of the covered work,
237 | and which are not combined with it such as to form a larger program,
238 | in or on a volume of a storage or distribution medium, is called an
239 | "aggregate" if the compilation and its resulting copyright are not
240 | used to limit the access or legal rights of the compilation's users
241 | beyond what the individual works permit. Inclusion of a covered work
242 | in an aggregate does not cause this License to apply to the other
243 | parts of the aggregate.
244 |
245 | 6. Conveying Non-Source Forms.
246 |
247 | You may convey a covered work in object code form under the terms
248 | of sections 4 and 5, provided that you also convey the
249 | machine-readable Corresponding Source under the terms of this License,
250 | in one of these ways:
251 |
252 | a) Convey the object code in, or embodied in, a physical product
253 | (including a physical distribution medium), accompanied by the
254 | Corresponding Source fixed on a durable physical medium
255 | customarily used for software interchange.
256 |
257 | b) Convey the object code in, or embodied in, a physical product
258 | (including a physical distribution medium), accompanied by a
259 | written offer, valid for at least three years and valid for as
260 | long as you offer spare parts or customer support for that product
261 | model, to give anyone who possesses the object code either (1) a
262 | copy of the Corresponding Source for all the software in the
263 | product that is covered by this License, on a durable physical
264 | medium customarily used for software interchange, for a price no
265 | more than your reasonable cost of physically performing this
266 | conveying of source, or (2) access to copy the
267 | Corresponding Source from a network server at no charge.
268 |
269 | c) Convey individual copies of the object code with a copy of the
270 | written offer to provide the Corresponding Source. This
271 | alternative is allowed only occasionally and noncommercially, and
272 | only if you received the object code with such an offer, in accord
273 | with subsection 6b.
274 |
275 | d) Convey the object code by offering access from a designated
276 | place (gratis or for a charge), and offer equivalent access to the
277 | Corresponding Source in the same way through the same place at no
278 | further charge. You need not require recipients to copy the
279 | Corresponding Source along with the object code. If the place to
280 | copy the object code is a network server, the Corresponding Source
281 | may be on a different server (operated by you or a third party)
282 | that supports equivalent copying facilities, provided you maintain
283 | clear directions next to the object code saying where to find the
284 | Corresponding Source. Regardless of what server hosts the
285 | Corresponding Source, you remain obligated to ensure that it is
286 | available for as long as needed to satisfy these requirements.
287 |
288 | e) Convey the object code using peer-to-peer transmission, provided
289 | you inform other peers where the object code and Corresponding
290 | Source of the work are being offered to the general public at no
291 | charge under subsection 6d.
292 |
293 | A separable portion of the object code, whose source code is excluded
294 | from the Corresponding Source as a System Library, need not be
295 | included in conveying the object code work.
296 |
297 | A "User Product" is either (1) a "consumer product", which means any
298 | tangible personal property which is normally used for personal, family,
299 | or household purposes, or (2) anything designed or sold for incorporation
300 | into a dwelling. In determining whether a product is a consumer product,
301 | doubtful cases shall be resolved in favor of coverage. For a particular
302 | product received by a particular user, "normally used" refers to a
303 | typical or common use of that class of product, regardless of the status
304 | of the particular user or of the way in which the particular user
305 | actually uses, or expects or is expected to use, the product. A product
306 | is a consumer product regardless of whether the product has substantial
307 | commercial, industrial or non-consumer uses, unless such uses represent
308 | the only significant mode of use of the product.
309 |
310 | "Installation Information" for a User Product means any methods,
311 | procedures, authorization keys, or other information required to install
312 | and execute modified versions of a covered work in that User Product from
313 | a modified version of its Corresponding Source. The information must
314 | suffice to ensure that the continued functioning of the modified object
315 | code is in no case prevented or interfered with solely because
316 | modification has been made.
317 |
318 | If you convey an object code work under this section in, or with, or
319 | specifically for use in, a User Product, and the conveying occurs as
320 | part of a transaction in which the right of possession and use of the
321 | User Product is transferred to the recipient in perpetuity or for a
322 | fixed term (regardless of how the transaction is characterized), the
323 | Corresponding Source conveyed under this section must be accompanied
324 | by the Installation Information. But this requirement does not apply
325 | if neither you nor any third party retains the ability to install
326 | modified object code on the User Product (for example, the work has
327 | been installed in ROM).
328 |
329 | The requirement to provide Installation Information does not include a
330 | requirement to continue to provide support service, warranty, or updates
331 | for a work that has been modified or installed by the recipient, or for
332 | the User Product in which it has been modified or installed. Access to a
333 | network may be denied when the modification itself materially and
334 | adversely affects the operation of the network or violates the rules and
335 | protocols for communication across the network.
336 |
337 | Corresponding Source conveyed, and Installation Information provided,
338 | in accord with this section must be in a format that is publicly
339 | documented (and with an implementation available to the public in
340 | source code form), and must require no special password or key for
341 | unpacking, reading or copying.
342 |
343 | 7. Additional Terms.
344 |
345 | "Additional permissions" are terms that supplement the terms of this
346 | License by making exceptions from one or more of its conditions.
347 | Additional permissions that are applicable to the entire Program shall
348 | be treated as though they were included in this License, to the extent
349 | that they are valid under applicable law. If additional permissions
350 | apply only to part of the Program, that part may be used separately
351 | under those permissions, but the entire Program remains governed by
352 | this License without regard to the additional permissions.
353 |
354 | When you convey a copy of a covered work, you may at your option
355 | remove any additional permissions from that copy, or from any part of
356 | it. (Additional permissions may be written to require their own
357 | removal in certain cases when you modify the work.) You may place
358 | additional permissions on material, added by you to a covered work,
359 | for which you have or can give appropriate copyright permission.
360 |
361 | Notwithstanding any other provision of this License, for material you
362 | add to a covered work, you may (if authorized by the copyright holders of
363 | that material) supplement the terms of this License with terms:
364 |
365 | a) Disclaiming warranty or limiting liability differently from the
366 | terms of sections 15 and 16 of this License; or
367 |
368 | b) Requiring preservation of specified reasonable legal notices or
369 | author attributions in that material or in the Appropriate Legal
370 | Notices displayed by works containing it; or
371 |
372 | c) Prohibiting misrepresentation of the origin of that material, or
373 | requiring that modified versions of such material be marked in
374 | reasonable ways as different from the original version; or
375 |
376 | d) Limiting the use for publicity purposes of names of licensors or
377 | authors of the material; or
378 |
379 | e) Declining to grant rights under trademark law for use of some
380 | trade names, trademarks, or service marks; or
381 |
382 | f) Requiring indemnification of licensors and authors of that
383 | material by anyone who conveys the material (or modified versions of
384 | it) with contractual assumptions of liability to the recipient, for
385 | any liability that these contractual assumptions directly impose on
386 | those licensors and authors.
387 |
388 | All other non-permissive additional terms are considered "further
389 | restrictions" within the meaning of section 10. If the Program as you
390 | received it, or any part of it, contains a notice stating that it is
391 | governed by this License along with a term that is a further
392 | restriction, you may remove that term. If a license document contains
393 | a further restriction but permits relicensing or conveying under this
394 | License, you may add to a covered work material governed by the terms
395 | of that license document, provided that the further restriction does
396 | not survive such relicensing or conveying.
397 |
398 | If you add terms to a covered work in accord with this section, you
399 | must place, in the relevant source files, a statement of the
400 | additional terms that apply to those files, or a notice indicating
401 | where to find the applicable terms.
402 |
403 | Additional terms, permissive or non-permissive, may be stated in the
404 | form of a separately written license, or stated as exceptions;
405 | the above requirements apply either way.
406 |
407 | 8. Termination.
408 |
409 | You may not propagate or modify a covered work except as expressly
410 | provided under this License. Any attempt otherwise to propagate or
411 | modify it is void, and will automatically terminate your rights under
412 | this License (including any patent licenses granted under the third
413 | paragraph of section 11).
414 |
415 | However, if you cease all violation of this License, then your
416 | license from a particular copyright holder is reinstated (a)
417 | provisionally, unless and until the copyright holder explicitly and
418 | finally terminates your license, and (b) permanently, if the copyright
419 | holder fails to notify you of the violation by some reasonable means
420 | prior to 60 days after the cessation.
421 |
422 | Moreover, your license from a particular copyright holder is
423 | reinstated permanently if the copyright holder notifies you of the
424 | violation by some reasonable means, this is the first time you have
425 | received notice of violation of this License (for any work) from that
426 | copyright holder, and you cure the violation prior to 30 days after
427 | your receipt of the notice.
428 |
429 | Termination of your rights under this section does not terminate the
430 | licenses of parties who have received copies or rights from you under
431 | this License. If your rights have been terminated and not permanently
432 | reinstated, you do not qualify to receive new licenses for the same
433 | material under section 10.
434 |
435 | 9. Acceptance Not Required for Having Copies.
436 |
437 | You are not required to accept this License in order to receive or
438 | run a copy of the Program. Ancillary propagation of a covered work
439 | occurring solely as a consequence of using peer-to-peer transmission
440 | to receive a copy likewise does not require acceptance. However,
441 | nothing other than this License grants you permission to propagate or
442 | modify any covered work. These actions infringe copyright if you do
443 | not accept this License. Therefore, by modifying or propagating a
444 | covered work, you indicate your acceptance of this License to do so.
445 |
446 | 10. Automatic Licensing of Downstream Recipients.
447 |
448 | Each time you convey a covered work, the recipient automatically
449 | receives a license from the original licensors, to run, modify and
450 | propagate that work, subject to this License. You are not responsible
451 | for enforcing compliance by third parties with this License.
452 |
453 | An "entity transaction" is a transaction transferring control of an
454 | organization, or substantially all assets of one, or subdividing an
455 | organization, or merging organizations. If propagation of a covered
456 | work results from an entity transaction, each party to that
457 | transaction who receives a copy of the work also receives whatever
458 | licenses to the work the party's predecessor in interest had or could
459 | give under the previous paragraph, plus a right to possession of the
460 | Corresponding Source of the work from the predecessor in interest, if
461 | the predecessor has it or can get it with reasonable efforts.
462 |
463 | You may not impose any further restrictions on the exercise of the
464 | rights granted or affirmed under this License. For example, you may
465 | not impose a license fee, royalty, or other charge for exercise of
466 | rights granted under this License, and you may not initiate litigation
467 | (including a cross-claim or counterclaim in a lawsuit) alleging that
468 | any patent claim is infringed by making, using, selling, offering for
469 | sale, or importing the Program or any portion of it.
470 |
471 | 11. Patents.
472 |
473 | A "contributor" is a copyright holder who authorizes use under this
474 | License of the Program or a work on which the Program is based. The
475 | work thus licensed is called the contributor's "contributor version".
476 |
477 | A contributor's "essential patent claims" are all patent claims
478 | owned or controlled by the contributor, whether already acquired or
479 | hereafter acquired, that would be infringed by some manner, permitted
480 | by this License, of making, using, or selling its contributor version,
481 | but do not include claims that would be infringed only as a
482 | consequence of further modification of the contributor version. For
483 | purposes of this definition, "control" includes the right to grant
484 | patent sublicenses in a manner consistent with the requirements of
485 | this License.
486 |
487 | Each contributor grants you a non-exclusive, worldwide, royalty-free
488 | patent license under the contributor's essential patent claims, to
489 | make, use, sell, offer for sale, import and otherwise run, modify and
490 | propagate the contents of its contributor version.
491 |
492 | In the following three paragraphs, a "patent license" is any express
493 | agreement or commitment, however denominated, not to enforce a patent
494 | (such as an express permission to practice a patent or covenant not to
495 | sue for patent infringement). To "grant" such a patent license to a
496 | party means to make such an agreement or commitment not to enforce a
497 | patent against the party.
498 |
499 | If you convey a covered work, knowingly relying on a patent license,
500 | and the Corresponding Source of the work is not available for anyone
501 | to copy, free of charge and under the terms of this License, through a
502 | publicly available network server or other readily accessible means,
503 | then you must either (1) cause the Corresponding Source to be so
504 | available, or (2) arrange to deprive yourself of the benefit of the
505 | patent license for this particular work, or (3) arrange, in a manner
506 | consistent with the requirements of this License, to extend the patent
507 | license to downstream recipients. "Knowingly relying" means you have
508 | actual knowledge that, but for the patent license, your conveying the
509 | covered work in a country, or your recipient's use of the covered work
510 | in a country, would infringe one or more identifiable patents in that
511 | country that you have reason to believe are valid.
512 |
513 | If, pursuant to or in connection with a single transaction or
514 | arrangement, you convey, or propagate by procuring conveyance of, a
515 | covered work, and grant a patent license to some of the parties
516 | receiving the covered work authorizing them to use, propagate, modify
517 | or convey a specific copy of the covered work, then the patent license
518 | you grant is automatically extended to all recipients of the covered
519 | work and works based on it.
520 |
521 | A patent license is "discriminatory" if it does not include within
522 | the scope of its coverage, prohibits the exercise of, or is
523 | conditioned on the non-exercise of one or more of the rights that are
524 | specifically granted under this License. You may not convey a covered
525 | work if you are a party to an arrangement with a third party that is
526 | in the business of distributing software, under which you make payment
527 | to the third party based on the extent of your activity of conveying
528 | the work, and under which the third party grants, to any of the
529 | parties who would receive the covered work from you, a discriminatory
530 | patent license (a) in connection with copies of the covered work
531 | conveyed by you (or copies made from those copies), or (b) primarily
532 | for and in connection with specific products or compilations that
533 | contain the covered work, unless you entered into that arrangement,
534 | or that patent license was granted, prior to 28 March 2007.
535 |
536 | Nothing in this License shall be construed as excluding or limiting
537 | any implied license or other defenses to infringement that may
538 | otherwise be available to you under applicable patent law.
539 |
540 | 12. No Surrender of Others' Freedom.
541 |
542 | If conditions are imposed on you (whether by court order, agreement or
543 | otherwise) that contradict the conditions of this License, they do not
544 | excuse you from the conditions of this License. If you cannot convey a
545 | covered work so as to satisfy simultaneously your obligations under this
546 | License and any other pertinent obligations, then as a consequence you may
547 | not convey it at all. For example, if you agree to terms that obligate you
548 | to collect a royalty for further conveying from those to whom you convey
549 | the Program, the only way you could satisfy both those terms and this
550 | License would be to refrain entirely from conveying the Program.
551 |
552 | 13. Use with the GNU Affero General Public License.
553 |
554 | Notwithstanding any other provision of this License, you have
555 | permission to link or combine any covered work with a work licensed
556 | under version 3 of the GNU Affero General Public License into a single
557 | combined work, and to convey the resulting work. The terms of this
558 | License will continue to apply to the part which is the covered work,
559 | but the special requirements of the GNU Affero General Public License,
560 | section 13, concerning interaction through a network will apply to the
561 | combination as such.
562 |
563 | 14. Revised Versions of this License.
564 |
565 | The Free Software Foundation may publish revised and/or new versions of
566 | the GNU General Public License from time to time. Such new versions will
567 | be similar in spirit to the present version, but may differ in detail to
568 | address new problems or concerns.
569 |
570 | Each version is given a distinguishing version number. If the
571 | Program specifies that a certain numbered version of the GNU General
572 | Public License "or any later version" applies to it, you have the
573 | option of following the terms and conditions either of that numbered
574 | version or of any later version published by the Free Software
575 | Foundation. If the Program does not specify a version number of the
576 | GNU General Public License, you may choose any version ever published
577 | by the Free Software Foundation.
578 |
579 | If the Program specifies that a proxy can decide which future
580 | versions of the GNU General Public License can be used, that proxy's
581 | public statement of acceptance of a version permanently authorizes you
582 | to choose that version for the Program.
583 |
584 | Later license versions may give you additional or different
585 | permissions. However, no additional obligations are imposed on any
586 | author or copyright holder as a result of your choosing to follow a
587 | later version.
588 |
589 | 15. Disclaimer of Warranty.
590 |
591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
599 |
600 | 16. Limitation of Liability.
601 |
602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
610 | SUCH DAMAGES.
611 |
612 | 17. Interpretation of Sections 15 and 16.
613 |
614 | If the disclaimer of warranty and limitation of liability provided
615 | above cannot be given local legal effect according to their terms,
616 | reviewing courts shall apply local law that most closely approximates
617 | an absolute waiver of all civil liability in connection with the
618 | Program, unless a warranty or assumption of liability accompanies a
619 | copy of the Program in return for a fee.
620 |
621 | END OF TERMS AND CONDITIONS
622 |
623 | How to Apply These Terms to Your New Programs
624 |
625 | If you develop a new program, and you want it to be of the greatest
626 | possible use to the public, the best way to achieve this is to make it
627 | free software which everyone can redistribute and change under these terms.
628 |
629 | To do so, attach the following notices to the program. It is safest
630 | to attach them to the start of each source file to most effectively
631 | state the exclusion of warranty; and each file should have at least
632 | the "copyright" line and a pointer to where the full notice is found.
633 |
634 | {one line to give the program's name and a brief idea of what it does.}
635 | Copyright (C) {year} {name of author}
636 |
637 | This program is free software: you can redistribute it and/or modify
638 | it under the terms of the GNU General Public License as published by
639 | the Free Software Foundation, either version 3 of the License, or
640 | (at your option) any later version.
641 |
642 | This program is distributed in the hope that it will be useful,
643 | but WITHOUT ANY WARRANTY; without even the implied warranty of
644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
645 | GNU General Public License for more details.
646 |
647 | You should have received a copy of the GNU General Public License
648 | along with this program. If not, see .
649 |
650 | Also add information on how to contact you by electronic and paper mail.
651 |
652 | If the program does terminal interaction, make it output a short
653 | notice like this when it starts in an interactive mode:
654 |
655 | Black Hat Arsenal Github Tools Copyright (C) 2017 ToolsWatch.org
656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
657 | This is free software, and you are welcome to redistribute it
658 | under certain conditions; type `show c' for details.
659 |
660 | The hypothetical commands `show w' and `show c' should show the appropriate
661 | parts of the General Public License. Of course, your program's commands
662 | might be different; for a GUI interface, you would use an "about box".
663 |
664 | You should also get your employer (if you work as a programmer) or school,
665 | if any, to sign a "copyright disclaimer" for the program, if necessary.
666 | For more information on this, and how to apply and follow the GNU GPL, see
667 | .
668 |
669 | The GNU General Public License does not permit incorporating your program
670 | into proprietary programs. If your program is a subroutine library, you
671 | may consider it more useful to permit linking proprietary applications with
672 | the library. If this is what you want to do, use the GNU Lesser General
673 | Public License instead of this License. But first, please read
674 | .
675 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # Official Black Hat Arsenal Tools Github Repository
2 |
3 | 
4 |
5 | This github account maps to the Black Hat Arsenal tools since its inception in 2011.
6 | For readibility, the tools are classified by category and not by session.
7 |
8 | This account is maintained by [ToolsWatch.org](https://www.toolswatch.org) the official organizer of the Black Hat Arsenal event
9 |
10 |
11 | **Disclaimer**: Tools not demonstrated during a Black Hat Arsenal session will not be accepted
12 |
13 | ### How to Submit ?
14 |
15 | Submit your template to the **most one representative categor**y as a pull request. After review, we will reflect the change on the repo.
16 | Use the given template `tool_name.md` .
17 | Change tool_name.md to your tool name (ex: lynis.md)
18 |
19 | ### Missing a category ?
20 |
21 | If you think we missed a category, do not hesitate to contact us (or push request).
22 |
23 | ### Contact us
24 |
25 | * [Twitter](https://twitter.com/toolswatch)
26 | * [Email](mailto:hacker@toolswatch.org)
--------------------------------------------------------------------------------
/code_assessment/puma_scan.md:
--------------------------------------------------------------------------------
1 | # Puma Scan
2 |
3 | ### Description
4 | Puma Scan is a software security Visual Studio analyzer extension built on top of Roslyn, the open-source .NET Compiler Platform. Puma Scan provides real time, continuous source code analysis as development teams write code. Vulnerabilities are immediately displayed in the development environment as spell check and compiler warnings, preventing security bugs from entering your applications. Simply install the plugin / NuGet package and find the following vulnerability patterns:
5 | * Command Injection (SQL, LDAP, OS Commands)
6 | * Cross-Site Scripting
7 | * Cross-Site Request Forgery
8 | * Insecure Cryptography
9 | * Insecure Password Management
10 | * Unvalidated Redirect
11 | * Weak Validation
12 | * Directory Traversal
13 | * Missing Certificate Validation
14 |
15 | ### Categories
16 | * Code Assessment
17 | * Static Analysis
18 | * .NET Security
19 |
20 | #### BlackHat Arsenal sessions
21 |
22 | [](https://www.toolswatch.org/2017/02/the-black-hat-arsenal-asia-2017-great-line-up/)
23 | [](https://www.toolswatch.org/2017/06/the-black-hat-arsenal-usa-2017-phenomenal-line-up-announced/)
24 |
25 |
26 | ### Code
27 | [https://github.com/pumasecurity/puma-scan](https://github.com/pumasecurity/puma-scan)
28 |
29 | ### Lead Developers
30 | * Eric Johnson ([@emjohn20](https://twitter.com/emjohn20)) - [https://pumascan.com/about.html](https://pumascan.com/about.html)
31 | * Eric Mead ([@ericmmead](https://twitter.com/ericmmead)) - [https://pumascan.com/about.html](https://pumascan.com/about.html)
32 | * Aaron Cure ([@curea](https://twitter.com/curea)) - [https://pumascan.com/about.html](https://pumascan.com/about.html)
33 |
34 | ### Social Media
35 | * [Twitter](https://twitter.com/puma_scan)
36 | * [Company Website](https://pumascan.com/)
37 |
--------------------------------------------------------------------------------
/cryptography/hashview.md:
--------------------------------------------------------------------------------
1 | # Hashview
2 |
3 | ### Description
4 | Hashview is a web front-end to hashcat with many powerful features geared towards penetration testers. Leverage task automation and real-time analytics for increased results and fancy reports.
5 |
6 | ### Categories
7 | * Cryptography
8 | * Penetration Testing
9 | * Reporting
10 |
11 | ### Black Hat sessions
12 | [](https://www.blackhat.com/us-17/arsenal/schedule/#hashview-8019)
13 |
14 | ### Code
15 | https://github.com/hashview/hashview
16 |
17 | ### Lead Developers
18 | * Hans lakhan - i128 https://github.com/i128
19 | * Casey Cammilleri - ccammilleri https://github.com/ccammilleri
20 |
21 | ### Social Media
22 | * [@jarsnah12](https://twitter.com/jarsnah12)
23 | * [@caseycammilleri](https://twitter.com/CaseyCammilleri)
24 | * [http://www.hashview.io](https://www.hashview.io/)
25 |
--------------------------------------------------------------------------------
/exploitation/avet.md:
--------------------------------------------------------------------------------
1 | # AVET
2 |
3 | ### Description
4 | AVET is an AntiVirus Evasion Tool, which was developed for making life easier for pentesters and for experimenting with antivirus evasion techniques.
5 |
6 | What & Why:
7 | - When running an exe file made with msfpayload & co, the exe file will often be recognized by the antivirus software
8 | - AVET is a antivirus evasion tool targeting windows machines
9 | - The techniques used in avet evaded most antivirus suites, including MS Defender, McAfee, Sophos, Avira and more
10 | - AVET includes two tools, avet.exe with different antivirus evasion techniques and make_avet for compiling a preconfigured binary file
11 | - For encoding the shellcode the tools format.sh and sh_format are included
12 | - AVET is tested with Kali 2 and tdm-gcc
13 | - Interactive assistant for easier usage
14 | - Support for 64bit payloads
15 | - The metasploit psexec module can be used
16 |
17 | ### Categories
18 | * Exploitation
19 | * Vulnerability assessment
20 | * Ethical Hacking
21 |
22 | ### Black Hat sessions
23 | [](https://www.toolswatch.org/2017/02/the-black-hat-arsenal-asia-2017-great-line-up/)
24 | [](http://www.toolswatch.org/2017/06/the-black-hat-arsenal-usa-2017-phenomenal-line-up-announced/)
25 |
26 | ### Code
27 | https://github.com/govolution/avet
28 |
29 | ### Lead Developer
30 | Daniel Sauder - https://github.com/govolution
31 |
32 | ### Social Media
33 | * [Twitter](https://twitter.com/DanielX4v3r)
34 | * [Blog](https://govolution.wordpress.com/)
35 |
--------------------------------------------------------------------------------
/exploitation/gef.md:
--------------------------------------------------------------------------------
1 | # GEF - GDB Enhanced Features
2 |
3 |
4 | ### Description
5 |
6 | `GEF` is a kick-ass set of GDB commands for X86, ARM, MIPS, PowerPC and SPARC to make
7 | GDB cool again for exploit dev. It is aimed to be used mostly by exploiters and reverse-engineers,
8 | to provide additional features to GDB using the Python API to assist during the process of
9 | dynamic analysis and exploit development.
10 |
11 | It has full support for both Python2 and Python3 indifferently (as more and more distros start
12 | pushing gdb compiled with Python3 support).
13 |
14 |
15 | ### Categories
16 |
17 | * Exploitation
18 | * Reverse-Engineering
19 | * Debugging
20 | * Capture-The-Flag
21 |
22 |
23 | ### Black Hat sessions
24 |
25 | [](http://www.toolswatch.org/2017/06/the-black-hat-arsenal-usa-2017-phenomenal-line-up-announced/)
26 |
27 |
28 | ### Code
29 | https://github.com/hugsy/gef.git
30 |
31 | ### Lead Developers
32 | * [hugsy](https://twitter.com/_hugsy_)
33 |
34 | Along with many contributors:
35 | * [GrazFather](https://twitter.com/Grazfather)
36 | * [Others](https://github.com/hugsy/gef/graphs/contributors)
37 |
38 | ### Social Media
39 | * IRC: Server:freenode.net Channel:##gef
40 | * WebIRC: https://webchat.freenode.net/?channels=##gef
41 | * [Documentation](https://gef.readthedocs.org/en/master/)
42 | * [Slides](https://blahcat.github.io/static/bhusa_2017/BH-USA-17-Alladoum-GDB-Enhanced-Features.pdf)
43 | * [Video Tutorials](https://www.youtube.com/playlist?list=PLjAuO31Rg972WeMvdR_57Qu-aVM8T6DkQ)
44 |
--------------------------------------------------------------------------------
/exploitation/mailsniper.md:
--------------------------------------------------------------------------------
1 | # MailSniper
2 |
3 | ### Description
4 | MailSniper is a PowerShell-based penetration testing tool whose primary purpose is to search through email in a Microsoft Exchange environment for specific terms (i.e. passwords, insider intel, network architecture information, etc.). It can be used as a non-administrative user to search their own email, or by an Exchange administrator to search the mailboxes of every user in a domain.
5 |
6 | MailSniper includes additional modules for attacking externally-facing Outlook Web Access (OWA) and Exchange Web Services (EWS) portals. With MailSniper, it is also possible to: perform password spraying attacks, enumerate internal domain names and usernames, locate inboxes with too broad permissions, and gather the Global Address List containing all email addresses of users at an organization from OWA and EWS.
7 |
8 | ### Categories
9 | * Exploitation
10 | * Network Attacks
11 |
12 | ### Black Hat sessions
13 |
14 | [](https://www.blackhat.com/us-17/arsenal/schedule/#mailsniper-7907)
15 |
16 | ### Code
17 | https://github.com/dafthack/MailSniper
18 |
19 | ### Lead Developer
20 | Beau Bullock
21 |
22 | ### Social Media
23 | * [Twitter](https://twitter.com/dafthack)
24 | * [Company Website](https://blackhillsinfosec.com/)
25 |
26 |
--------------------------------------------------------------------------------
/exploitation/rattler.md:
--------------------------------------------------------------------------------
1 | # Rattler
2 |
3 | ### Description
4 | Rattler is a tool that automates the identification of DLL's which can be used for DLL preloading attacks.
5 | Rattler enumerates an EXE's DLL's at runtime and provides a list of vulnerable DLL's which can be exploited for a preloading attack against the target application.
6 |
7 | ### Categories
8 | * Exploitation
9 | * Ethical Hacking
10 | * Vulnerability assessment
11 |
12 | ### Black Hat sessions
13 | [](http://www.toolswatch.org/2017/06/the-black-hat-arsenal-usa-2017-phenomenal-line-up-announced/)
14 |
15 | ### Code
16 | https://github.com/sensepost/rattler
17 |
18 | ### Lead Developer
19 | Chris Le Roy - SensePost https://github.com/sensepost
20 |
21 | ### Social Media
22 | * [Twitter](https://twitter.com/brompwnie)
23 | * [Company Website](https://sensepost.com)
24 |
25 |
--------------------------------------------------------------------------------
/forensics/inVtero.net.md:
--------------------------------------------------------------------------------
1 | # [inVtero.net](https://github.com/ShaneK2/inVtero.net)
2 |
3 | ## Description
4 | inVtero.net: A high speed (Gbps) Forensics, Memory integrity & assurance. Includes offensive & defensive memory capabilities.
5 | Find/Extract processes, hypervisors (including nested) in memory dumps using microarchitechture independent Virtual Machiene Introspection
6 | techniques
7 |
8 | Supports: VMWare (client/servers), XEN and physical systems (PAGEDUMP).
9 |
10 | #### Integrity
11 | Users can manage their own "golden images" of secure hashes used to ensure no byte slipps through the cracks
12 | of a forensic, reverse engineering, sandbox analysis or host integrity monitoring operation.
13 |
14 | We've recently added cloud hosted bitmaps and are expanding this to allow users to use the integrity funtionality without having to construct
15 | a database first.
16 |
17 | The block based integrity checks occur at a configurable size and will isolate very small code patches quickly.
18 |
19 | Integrity checking provides confidence to useres that they have analyzed "everything" and they have not wasted
20 | time looking in the wrong plaes.
21 |
22 | #### Memory Hacking
23 | An IronPython shell is able to use native type reflection that allwos for reading and writing physical memory dumps. Test a new
24 | kernel patch or improve inVtero itself. (e.g. edit _EPROCESS objects from python and write them back to a VM image then resume
25 | exection to observe DMA style hacking with very easy scripts that map 1:1 to known symbol sources)
26 |
27 | Recent modules include a Gargoyle detection mechanism that uses the type information extracted from the systems to allow for
28 | an exhaustive verification of thread stack states that can detect the preseanse of RoP type _weird machienes_.
29 |
30 | #### Performance
31 | A goal of the project is to provide high quality assurace as quickly as possiable. To avoid the common pitfall of many debuggers
32 | and forensic platforms that are trivially compromised.
33 |
34 | ### Categories
35 | * Forensics
36 | * Debugger (Passive memory debugging/hacking)
37 | * Malware HIDS (Integrity Monitoring)
38 | * Reverse Engineering
39 |
40 | ### Black Hat sessions
41 | [](http://www.toolswatch.org/2017/06/the-black-hat-arsenal-usa-2017-phenomenal-line-up-announced/)
42 |
43 | ### Code
44 | https://github.com/ShaneK2/inVtero.net
45 |
46 | ### Lead Developer
47 | K2 - https://github.com/K2
48 |
49 | ### Social Media
50 | * [Twitter](https://twitter.com/ktwo_K2)
51 | ----
52 | 
53 |
--------------------------------------------------------------------------------
/forensics/userline.md:
--------------------------------------------------------------------------------
1 | # Userline
2 |
3 | ### Description
4 | This tool automates the process of creating logon relations from MS Windows Security Events by showing a graphical relation among users domains, source and destination logons, session duration, who was logged on the systems in a given datetime, session hijacking, etc. It is also able to integrate with 3rd party tools and provides different output modes such as CSV output, Neo4j, Timesketch, JSON, SQLite, Gephi and Graphviz.
5 |
6 | ### Categories
7 | * Data Forensics
8 | * Incident Response
9 |
10 | ### Black Hat sessions
11 | [](http://www.toolswatch.org/2017/06/the-black-hat-arsenal-usa-2017-phenomenal-line-up-announced/)
12 |
13 | ### Code
14 | https://github.com/thiber-org/userline
15 |
16 | ### Lead Developer
17 | Chema Garcia - https://github.com/sch3m4
18 |
19 | ### Social Media
20 | * [Twitter](https://twitter.com/sch3m4)
21 | * [Company Website](http://thiber.org)
22 |
--------------------------------------------------------------------------------
/frameworks/defplorex.md:
--------------------------------------------------------------------------------
1 | # DefPloreX
2 |
3 | ### Description
4 | An Elasticsearch-based toolkit that our team uses for large-scale processing, analysis and visualization of e-crime records. In particular, we've successfully been applying DefPloreX to the analysis of deface records (e.g., from web compromises); hence its name, Def(acement) eXPlorer (DefPloreX).
5 |
6 | The full version of DefPloreX includes:
7 |
8 | * A thin wrapper to interact with an Elasticsearch backend (included in this release)
9 | * A distributed data-processing pipeline based on Celery (example included in this release)
10 | * An analysis component to extract information from deface web pages
11 | * A features extraction component to produce a compact, numerical and categorical representation of each web page
12 | * A statistical machine-learning component to automatically find groups of similar web pages
13 |
14 | The input to DefPloreX is a feed of URLs describing the deface web pages,
15 | including metadata such as the (declared) attacker name, timestamp, reason
16 | for hacking that page, and so on. Separately, we also have a mirror of the
17 | web pages at the time of compromise.
18 |
19 | ### Categories
20 | * OSINT
21 | * Frameworks
22 |
23 | ### Black Hat sessions
24 | [](http://www.toolswatch.org/2017/06/the-black-hat-arsenal-usa-2017-phenomenal-line-up-announced/)
25 |
26 | ### Code
27 | https://github.com/trendmicro/defplorex
28 |
29 | ### Lead Developer(s)
30 | Federico Maggi - Trend Micro https://github.com/phretor
31 | Marco Balduzzi - Trend Micro https://github.com/embyte
32 | Vincenzo Ciancaglini - Trend Micro
33 | Lion Gu - Trend Micro
34 | Ryan Flores - Trend Micro
35 |
36 |
37 | ### Social Media
38 | * [Twitter](https://twitter.com/trendlabs)
39 | * [DefPloreX blog post](http://blog.trendmicro.com/trendlabs-security-intelligence/defplorex-machine-learning-toolkit-large-scale-ecrime-forensics/)
40 |
--------------------------------------------------------------------------------
/frameworks/dradis_framework.md:
--------------------------------------------------------------------------------
1 | # Dradis Framework
2 |
3 | ### Description
4 | Dradis is an extensible, cross-platform, open source collaboration framework for InfoSec teams. It can import from over 19 popular tools, including Nessus, Qualys, Burp and AppScan. Started in 2007 (this is the 10th year anniversary!), Dradis Framework has been growing ever since (10,000+ commits in the last 12 months). Dradis is the best tool to combine the output of different scanners, add your manual findings and evidence and generate a report with one click.
5 |
6 | Free forever and open source.
7 |
8 | ### Categories
9 | * Collaboration
10 | * Reporting
11 | * Frameworks
12 |
13 | ### Black Hat sessions
14 | [](https://www.toolswatch.org/2014/09/lineup-for-the-blackhat-arsenal-europe-2014/)
15 | [](https://www.toolswatch.org/2015/06/black-hat-arsenal-usa-2015-speakers-lineup/)
16 | [](https://www.blackhat.com/us-16/arsenal.html#dradis-framework)
17 | [](http://www.toolswatch.org/2017/06/the-black-hat-arsenal-usa-2017-phenomenal-line-up-announced/)
18 |
19 |
20 | ### Code
21 | https://github.com/dradis/dradis-ce
22 |
23 | ### Lead Developers
24 | * Daniel Martin - Security Roots https://github.com/etdsoft
25 | * Xavi Vila - Security Roots https://github.com/dormi
26 | * Aaron Manaloto - Security Roots https://github.com/aapomm
27 |
28 | ### Social Media
29 | * [Forum](http://discuss.dradisframework.org)
30 | * [Twitter](https://twitter.com/dradisfw)
31 | * [Website](http://dradisframework.org/ce/?utm_source=github&utm_medium=web&utm_campaign=arsenal-tools)
32 |
--------------------------------------------------------------------------------
/frameworks/kubebot.md:
--------------------------------------------------------------------------------
1 | # Kubebot
2 |
3 | ### Description
4 | Kubebot is an automated scalable security testing framework based on a microservice architecture. Requests are sent to an API server which then orchestrates running the tools as Docker containers on a Kubernetes (K8S) backend. These requests are asynchronous i.e. they get dropped in a queue which are then picked up by Subscription workers. The subscription workers start the job of running the tools. The results of running those tools are diff'ed and only the changes are sent back to the fronend.
5 |
6 | Kubebot uses Slack as the frontend - as a way to send API requests but this can be extended into different frontends as well.
7 |
8 | Kubebot also gives the flexibility of setting up scheduled job runs using the K8S cronjob.
9 |
10 |
11 | ### Categories
12 | * Frameworks
13 | * Security Testing
14 | * BugBounty
15 | * Automation
16 | * Containers
17 |
18 |
19 | ### Black Hat sessions
20 | [](http://www.toolswatch.org/2017/06/the-black-hat-arsenal-usa-2017-phenomenal-line-up-announced/)
21 |
22 |
23 | ### Code
24 | https://github.com/anshumanbh/kubebot
25 |
26 |
27 | ### Lead Developer
28 | Anshuman Bhartiya - anshumanbh https://github.com/anshumanbh
29 |
30 | ### Social Media
31 | * [Twitter](https://twitter.com/anshuman_bh)
32 | * [DevSecOps](https://github.com/devsecops)
33 |
--------------------------------------------------------------------------------
/hardening/lynis.md:
--------------------------------------------------------------------------------
1 | # Lynis
2 |
3 | ### Description
4 | Lynis is a security auditing tool for sytems running Linux, macOS, BSD, and other flavors of Unix. The tool performs an in-depth security scan and runs on the system itself. The primary goal is to test security defenses and provide tips for further system hardening. It will also scan for general system information, vulnerable software packages, and possible configuration issues. As Lynis is written in POSIX shell script, it is light on resources and low on dependencies. This makes the tool great for putting it in build pipelines, running it as part of a forensics task or as penetration testing tool during an assignment.
5 |
6 | ### Categories
7 | * Hardening
8 | * Vulnerability assessment
9 |
10 | ### Black Hat sessions
11 | [](https://www.toolswatch.org/2014/09/lineup-for-the-blackhat-arsenal-europe-2014/)
12 | [](https://www.toolswatch.org/2015/06/black-hat-arsenal-usa-2015-speakers-lineup/)
13 | [](http://www.toolswatch.org/2016/09/the-black-hat-arsenal-europe-2016-line-up/)
14 |
15 | ### Popularity
16 |
17 | ToolsWatch Annual Best Free/Open Source Security Tool Survey:
18 |
19 | [](https://www.toolswatch.org/2013/12/2013-top-security-tools-as-voted-by-toolswatch-org-readers)
20 | [](https://www.toolswatch.org/2015/01/2014-top-security-tools-as-voted-by-toolswatch-org-readers)
21 | [](https://www.toolswatch.org/2016/02/2015-top-security-tools-as-voted-by-toolswatch-org-readers)
22 | [](https://www.toolswatch.org/2017/02/2016-top-security-tools-as-voted-by-toolswatch-org-readers)
23 |
24 | ### Code
25 | https://github.com/CISOfy/lynis
26 |
27 | ### Lead Developer
28 | Michael Boelen - CISOfy https://github.com/CISOfy
29 |
30 | ### Social Media
31 | * [Twitter](https://twitter.com/mboelen)
32 | * [Project page](https://cisofy.com/lynis/)
33 |
--------------------------------------------------------------------------------
/hardware_iot/.keep:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/whid-injector/blackhat-arsenal-tools/ef013459fd21b22ff63bd9c9a351d30389c47e4a/hardware_iot/.keep
--------------------------------------------------------------------------------
/hardware_iot/WHID.md:
--------------------------------------------------------------------------------
1 | # WHID Injector
2 |
3 | ### Description
4 | Since the first public appearance of HID Attacks, many awesome researches, tools and devices have been released.
5 | However, Offensive Security folks were always seeking a cheap and dedicated hardware that could be controlled remotely (i.e. over WiFi or BT).
6 | This is how WHID Injector was born.
7 | WHID stands for WiFi-HID injector, it is an USB-Rubberducky / Bad-USB on steroids, designed to fulfill RedTeamers needs during their engagements.
8 | Based on an Atmega 32u4 (i.e. Keyboard, mouse and serial emulation) and a ESP-12 (i.e. Wifi AP/Client), It can be easily controlled over the WiFi network and potentially bypass air-gapped environments.
9 |
10 | ### Categories
11 | * Hardware IoT
12 | * RedTeam
13 |
14 | ### Black Hat sessions
15 |
16 | [](https://www.toolswatch.org/2017/09/black-hat-arsenal-europe-2017-lineup/)
17 |
18 | ### Code
19 | https://github.com/whid-injector/WHID
20 |
21 | ### Lead Developer(s)
22 | Luca Bongiorni - https://twitter.com/LucaBongiorni
23 |
24 | Corey Harding - https://twitter.com/exploit_agency
25 |
26 | ### Social Media
27 | * [Medium](https://medium.com/@LucaBongiorni)
28 | * [GitHub](https://github.com/whid-injector)
29 |
--------------------------------------------------------------------------------
/ics_scada/.keep:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/whid-injector/blackhat-arsenal-tools/ef013459fd21b22ff63bd9c9a351d30389c47e4a/ics_scada/.keep
--------------------------------------------------------------------------------
/malware_research/.keep:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/whid-injector/blackhat-arsenal-tools/ef013459fd21b22ff63bd9c9a351d30389c47e4a/malware_research/.keep
--------------------------------------------------------------------------------
/malware_research/ProcInfo.md:
--------------------------------------------------------------------------------
1 | # Proc Info Lib
2 |
3 | ### Description
4 | Proc Info is an open-source, user-mode, process library for macOS. It provides simple interface to retrieve detailed information about running processes, plus allows one to asynchronously monitor process creation & exit events.
5 |
6 | Using this library, one can track processes during [malware analysis](https://speakerdeck.com/patrickwardle/fruitfly-via-a-custom-c-and-c-server?slide=17) or during [bug hunting](https://speakerdeck.com/patrickwardle/defcon-2017-death-by-1000-installers-its-all-broken?slide=20).
7 |
8 |
9 | ### Categories
10 | * Malware Research
11 | * Exploitation
12 | * Hardening
13 |
14 |
15 | ### Black Hat sessions
16 | [](http://www.toolswatch.org/2017/06/the-black-hat-arsenal-usa-2017-phenomenal-line-up-announced/)
17 |
18 | ### Code
19 | https://github.com/objective-see/ProcInfo
20 | https://github.com/objective-see/ProcInfoExample
21 |
22 | ### Lead Developer
23 | Patrick Wardle - Objective-See
24 |
25 | ### Social Media
26 | * [Twitter](https://twitter.com/patrickwardle)
27 | * [Company Website](https://objective-see.com)
28 |
29 |
--------------------------------------------------------------------------------
/malware_research/floss.md:
--------------------------------------------------------------------------------
1 | # FireEye Labs Obfuscated String Solver (FLOSS)
2 |
3 | ### Description
4 | The FireEye Labs Obfuscated String Solver (FLOSS) is an open source tool that automatically detects, extracts, and decodes obfuscated strings in Windows Portable Executable (PE) files. Malware analysts, forensic investigators, and incident responders can use FLOSS to quickly extract sensitive strings to identify indicators of compromise (IOCs). Malware authors encode strings in their programs to hide malicious capabilities and impede reverse engineering. Even simple encoding schemes defeat the ‘strings’ tool and complicate static and dynamic analysis. FLOSS uses advanced static analysis techniques, such as emulation, to deobfuscate encoded strings.
5 |
6 | FLOSS is extremely easy to use and works against a large corpus of malware. It follows a similar invocation as the ‘strings’ tool. Users that understand how to interpret the strings found in a binary will understand FLOSS’s output. FLOSS extracts higher value strings, as strings that are obfuscated typically contain the most sensitive configuration resources – including C2 server addresses, names of dynamically resolved imports, suspicious file paths, and other IOCs.
7 |
8 | ### Categories
9 | * Malware analysis
10 | * Malware research
11 | * Reverse engineering
12 |
13 | ### Black Hat sessions
14 | [](https://www.toolswatch.org/2016/06/the-black-hat-arsenal-usa-2016-remarkable-line-up/)
15 | [](https://www.toolswatch.org/2016/09/the-black-hat-arsenal-europe-2016-line-up/)
16 |
17 | ### Code
18 | https://github.com/fireeye/flare-floss
19 |
20 | ### Lead Developers
21 | * William Ballenthin - @williballenthin
22 | * Moritz Raabe - @m_r_tz
23 |
24 | ### Social Media
25 | * [@williballenthin](https://twitter.com/williballenthin)
26 | * [@m_r_tz](https://twitter.com/m_r_tz)
27 | * [FireEye Website](https://www.fireeye.com/)
28 |
29 |
--------------------------------------------------------------------------------
/malware_research/sniffMK.md:
--------------------------------------------------------------------------------
1 | # SniffMK
2 |
3 | ### Description
4 | SniffMK is a simple utility designed to sniff mouse and keyboard events on macOS. It is based on code from Amit Singh's [website](http://osxbook.com)
5 |
6 | SniffMK was designed to facilitate malware analysis (specifically OSX/FruitFly which can simulate both mouse and keyboard events) See BlackHat/DefCon [slides](https://speakerdeck.com/patrickwardle/fruitfly-via-a-custom-c-and-c-server?slide=18) for details.
7 |
8 |
9 | ### Categories
10 | * Malware Research
11 |
12 |
13 | ### Black Hat sessions
14 | [](http://www.toolswatch.org/2017/06/the-black-hat-arsenal-usa-2017-phenomenal-line-up-announced/)
15 |
16 | ### Code
17 | https://github.com/objective-see/sniffMK
18 |
19 | ### Lead Developer
20 | Patrick Wardle - Objective-See
21 |
22 | ### Social Media
23 | * [Twitter](https://twitter.com/patrickwardle)
24 | * [Company Website](https://objective-see.com)
25 |
26 |
--------------------------------------------------------------------------------
/mobile_hacking/androidtamer.md:
--------------------------------------------------------------------------------
1 | # Android Tamer
2 |
3 | ### Description
4 | Android Tamer project provides various resources for Android mobile application and device security reviews. Be it pentesting, malware analysis, reverse engineering or device assessment. We strive to solve some of the major pain points in setting up the testing environments by providing various ways and means to perform the task in most effortless manner possible.
5 |
6 | ### Categories
7 | * Mobile Security
8 | * Vulnerability assessment
9 | * Penetration Testing
10 |
11 | ### Black Hat sessions
12 | [](https://www.toolswatch.org/2015/10/black-hat-arsenal-europe-2015-line-up/)
13 | [](https://www.toolswatch.org/2016/06/the-black-hat-arsenal-usa-2016-remarkable-line-up/)
14 | [](https://www.toolswatch.org/2017/06/the-black-hat-arsenal-usa-2017-phenomenal-line-up-announced/)
15 |
16 | ### Code
17 | https://github.com/AndroidTamer/AndroidTamer
18 |
19 | ### Lead Developers
20 | * Anant Shrivastava - https://github.com/Anantshri
21 | * Chandrapal - https://github.com/Chan9390
22 | * Rahul Binjve - https://github.com/c0dist
23 |
24 | ### Social Media
25 | * [Official Website](https://androidtamer.com/)
26 | * [Twitter](https://twitter.com/AndroidTamer)
27 | * [Facebook](https://facebook.com/AndroidTamer)
28 |
--------------------------------------------------------------------------------
/mobile_hacking/badintent.md:
--------------------------------------------------------------------------------
1 | # BadIntent
2 |
3 | ### Description
4 | BadIntent integrates Android's Binder framework with Burp Suite. It enables pentesters to use the typical Burp Suite workflow and all of its tools and extensions. BadIntent helps in identifying vulnerabilities, makes AIDL-attacks more easy to perform and assists in attacks against backends. Since Binder transactions are hooked, it is possible to analyze, interrupt, modify and repeat most communication channels and exchanged messages. This can be used for reverse engineering and obfuscation bypass activities.
5 |
6 | ### Categories
7 | * Mobile Security
8 | * Penetration Testing
9 | * Reverse Engineering
10 |
11 | ### Black Hat sessions
12 | [](https://www.blackhat.com/us-17/arsenal/schedule/#badintent---integrating-android-with-burp-8044)
13 |
14 |
15 | ### Code
16 | https://github.com/mateuszk87/BadIntent
17 |
18 | ### Lead Developer
19 | Mateusz Khalil - https://github.com/mateuszk87/
20 |
21 | ### Social Media
22 | * [Twitter](https://twitter.com/mateuszk87)
23 | * [LinkedIn](https://linkedin.com/in/mateusz-khalil-2bb885a0)
24 |
25 |
26 |
--------------------------------------------------------------------------------
/mobile_hacking/kwetza.md:
--------------------------------------------------------------------------------
1 | # Kwetza
2 |
3 | ### Description
4 | Kwetza is a tool that allows you to infect an existing Android application with a Meterpreter payload. Kwetza allows you to infect Android applications using the target application's default permissions or inject additional permissions to gain additional functionality.
5 |
6 |
7 | ### Categories
8 | * Mobile Security
9 | * Mobile Malware
10 |
11 | ### Black Hat sessions
12 |
13 | [](http://www.toolswatch.org/2017/06/the-black-hat-arsenal-usa-2017-phenomenal-line-up-announced/)
14 |
15 | ### Code
16 | https://github.com/sensepost/kwetza
17 |
18 | ### Lead Developer
19 | Chris Le Roy - SensePost https://github.com/sensepost
20 |
21 | ### Social Media
22 | * [Twitter](https://twitter.com/brompwnie)
23 | * [Company Website](https://sensepost.com/)
24 |
25 |
--------------------------------------------------------------------------------
/mobile_hacking/mobsf.md:
--------------------------------------------------------------------------------
1 | # MobSF
2 |
3 | ### Description
4 | Mobile Security Framework (MobSF) is an intelligent, all-in-one open source mobile application (Android/iOS/Windows) automated pen-testing framework capable of performing static and dynamic analysis. It can be used for effective and fast security analysis of Android, iOS and Windows mobile Applications and supports both binaries (APK, IPA & APPX ) and zipped source code. MobSF can also perform Web API Security testing with it's API Fuzzer that can do Information Gathering, analyze Security Headers, identify Mobile API specific vulnerabilities like XXE, SSRF, Path Traversal, IDOR, and other logical issues related to Session and API Rate Limiting.
5 |
6 | ### Categories
7 | * Mobile Security
8 | * SAST & DAST
9 | * Malware Analysis
10 | * Web API Security
11 | * Vulnerability assessment
12 |
13 | ### Black Hat sessions
14 |
15 | [](https://www.toolswatch.org/2015/03/black-hat-asia-2015-arsenal-speaker-list/)
16 |
17 |
18 | ### Code
19 | https://github.com/MobSF/Mobile-Security-Framework-MobSF/
20 |
21 | ### Lead Developer
22 | Ajin Abraham - OpenSecurity https://github.com/ajinabraham
23 |
24 | ### Social Media
25 | * [Twitter](https://twitter.com/ajinabraham)
26 | * [LinkedIn](https://in.linkedin.com/in/ajinabraham)
27 | * [Website](https://ajinabraham.com/)
28 |
29 |
30 |
--------------------------------------------------------------------------------
/mobile_hacking/needle.md:
--------------------------------------------------------------------------------
1 | # Needle
2 |
3 | ### Description
4 |
5 | Needle is the MWR's iOS Security Testing Framework, released at Black Hat USA in August 2016. It is an open source modular framework which aims to streamline the entire process of conducting security assessments of iOS applications, and acts as a central point from which to do so. Given its modular approach, Needle is easily extensible and new modules can be added in the form of python scripts. Needle is intended to be useful not only for security professionals, but also for developers looking to secure their code. A few examples of testing areas covered by Needle include: data storage, inter-process communication, network communications, static code analysis, hooking and binary protections. The only requirement in order to run Needle effectively is a jailbroken device.
6 |
7 | With the release of Needle v1.0.0, we provided a major overhaul of its core and the introduction of a new native agent, written entirely in Objective-C. The new NeedleAgent is an open source iOS app complementary to Needle, that will allow it to programmatically perform tasks natively on the device, eliminating the need for third party tools.
8 |
9 | ### Categories
10 |
11 | * Mobile Security
12 | * Vulnerability assessment
13 | * Penetration Testing
14 |
15 | ### Black Hat sessions
16 |
17 | [](https://www.toolswatch.org/2016/06/the-black-hat-arsenal-usa-2016-remarkable-line-up/)
18 | [](https://www.toolswatch.org/2016/09/the-black-hat-arsenal-europe-2016-line-up/)
19 | [](http://www.toolswatch.org/2017/06/the-black-hat-arsenal-usa-2017-phenomenal-line-up-announced/)
20 |
21 | ### Code
22 |
23 | * https://github.com/mwrlabs/needle
24 | * https://github.com/mwrlabs/needle-agent
25 |
26 | ### Lead Developer
27 |
28 | Marco Lancini - https://github.com/marco-lancini
29 |
30 | ### Social Media
31 |
32 | * [Twitter](https://twitter.com/mwrneedle)
33 | * [Company Website](https://labs.mwrinfosecurity.com/)
34 |
--------------------------------------------------------------------------------
/network_attacks/crowbar.md:
--------------------------------------------------------------------------------
1 | # Crowbar
2 |
3 | ### Description
4 | Crowbar (formally known as Levye) is a brute forcing tool that can be used during penetration tests. It was developed to brute force some protocols in a different manner according to other popular brute forcing tools. As an example, while most brute forcing tools use username and password for SSH brute force, Crowbar uses SSH key(s). This allows for any private keys that have been obtained during penetration tests, to be used to attack other SSH servers.
5 |
6 | Currently Crowbar supports:
7 |
8 | OpenVPN
9 | Remote Desktop Protocol (RDP) with NLA support
10 | SSH private key authentication
11 | VNC key authentication
12 |
13 |
14 | ### Categories
15 | * Network Attacks
16 |
17 |
18 | ### Black Hat sessions
19 | [](https://www.blackhat.com/us-14/arsenal.html#Alkan)
20 | [](http://www.blackhat.com/us-15/arsenal.html#heybe-pentest-automation-toolkit)
21 |
22 |
23 | ### Code
24 | https://github.com/galkan/crowbar
25 |
26 |
27 | ### Lead Developer
28 | * Gokhan Alkan - https://github.com/galkan
29 |
30 |
31 | ### Social Media
32 | * [Twitter](https://twitter.com/gokhan_alkn)
33 |
--------------------------------------------------------------------------------
/network_attacks/delta.md:
--------------------------------------------------------------------------------
1 | # DELTA
2 |
3 | ### Description
4 | DELTA is a first SDN security evaluation framework, which has two primary functions; (1) It can automatically instantiate attack cases against SDN elements across diverse environments, and (2) it can assist in uncovering unknown security problems within an SDN deployment by using a blackbox fuzzing technique. For replaying attack cases, our framework has a number of test cases against popular SDN controllers and all SDN-enabled switch devices (software and hardware). Also, our framework provides a protocol-aware fuzzer for OpenFlow, which is a de-facto standard protocol of SDN, in order to find new vulnerabilities in SDNs.
5 |
6 | ### Categories
7 | * Network Attacks
8 | * Vulnerability assessment
9 | * Frameworks
10 |
11 | ### Black Hat sessions
12 | [](https://www.blackhat.com/us-17/arsenal/schedule/#delta-sdn-security-evaluation-framework-7466)
13 |
14 | ### Code
15 | https://github.com/OpenNetworkingFoundation/DELTA
16 |
17 | ### Lead Developers
18 | * Seungsoo Lee [seungsoo-lee] - https://github.com/seungsoo-lee
19 | * Jinwoo Kim [jinwoookim] - https://github.com/jinwoookim
20 |
21 | ### Social Media
22 | * [Laboratory Website](http://nss.kaist.ac.kr/)
23 |
--------------------------------------------------------------------------------
/network_attacks/det.md:
--------------------------------------------------------------------------------
1 | # DET
2 |
3 | ### Description
4 | DET aims to provide a framework to assist with exfiltrating data using either one or several channels. Social media has become extremely popular in recent attacks such as HammerToss, campaign uncovered by FireEye in July 2015. Several tools are also publicly available allowing you to remotely access computers through "legitimate" services such as Gmail (GCat) or Twitter (Twittor). Often gaining access to a network is just the first step for a targeted attacker. Once inside, the goal is to go after sensitive information and exfiltrate it to servers under their control. To prevent this from occuring, a whole industry has popped up with the aim of stopping exfiltration attacks. However, often these are expensive and rarely work as expected. With this in mind, I created the Data Exfiltration Toolkit (DET) to help both penetration testers testing deployed security devices and those admins who've installed and configured them, to ensure they are working as expected and detecting when sensitive data is leaving the network.
5 |
6 |
7 | ### Categories
8 | * Network Attacks
9 | * Frameworks
10 |
11 | ### Black Hat sessions
12 | [](https://www.blackhat.com/us-16/arsenal.html#det)
13 |
14 | ### Code
15 | https://github.com/PaulSec/DET
16 |
17 | ### Lead Developer
18 | * Paul Amar (@PaulWebSec) - https://github.com/PaulSec
19 |
20 | ### Social Media
21 | * [@PaulWebSec](https://twitter.com/PaulWebSec)
22 |
--------------------------------------------------------------------------------
/network_attacks/eaphammer.md:
--------------------------------------------------------------------------------
1 | # EAPHammer
2 |
3 | ### Description
4 | EAPHammer is a toolkit for performing targeted evil twin attacks against WPA2-Enterprise networks. It is designed to be used in full scope wireless assessments and red team engagements. As such, focus is placed on providing an easy-to-use interface that can be leveraged to execute powerful wireless attacks with minimal manual configuration. To illustrate how fast this tool is, here's an example of how to setup and execute a credential stealing evil twin attack against a WPA2-TTLS network in just two commands:
5 |
6 | # generate certificates
7 | ./eaphammer --cert-wizard
8 |
9 | # launch attack
10 | ./eaphammer -i wlan0 --channel 4 --auth ttls --wpa 2 --essid CorpWifi --creds
11 |
12 | EAPHammer is also equipped to perform two new attacks [first presented at DEF CON 25](https://media.defcon.org/DEF%20CON%2025/DEF%20CON%2025%20presentations/DEFCON-25-Gabriel-Ryan-The-Black-Art-of-Wireless-Post-Exploitation-UPDATED.pdf):
13 | - __Hostile Portal Attacks:__ Steal Active Directory credentials without direct network access
14 | - __Indirect Wireless Pivots:__ Bypass port-based access controls using rogue access point attacks
15 |
16 | Leverages a [lightly modified](https://github.com/s0lst1c3/hostapd-eaphammer) version of [hostapd-wpe](https://github.com/opensecurityresearch/hostapd-wpe) (shoutout to [Brad Anton](https://github.com/brad-anton) for creating the original), _dnsmasq_, [Responder](https://github.com/SpiderLabs/Responder), and _Python 2.7_.
17 |
18 | ### Categories
19 | * Wireless
20 | * Red Team
21 | * Rogue Access Point Attacks
22 | * WPA-EAP/WPA2-EAP
23 |
24 | ### Black Hat sessions
25 | [](https://www.blackhat.com/us-17/arsenal.html#eaphammer)
26 |
27 | ### Code
28 | https://github.com/s0lst1c3/eaphammer
29 |
30 | ### Lead Developer
31 | Gabriel Ryan - s0lst1c3 https://github.com/s0lst1c3
32 |
33 | ### Social Media
34 | * [Twitter](https://twitter.com/s0lst1c3)
35 | * [LinkedIn](linkedin.com/in/ms08067)
36 | * [Blog Posts: GDS Labs](https://blog.gdssecurity.com/labs/author/gryan)
37 | * [Blog Posts: Personal](http://solstice.me/about/)
38 | ----
39 |
--------------------------------------------------------------------------------
/network_attacks/egression.md:
--------------------------------------------------------------------------------
1 | # Egression
2 |
3 | ### Description
4 | Egression is a utility for testing the data loss prevention controls on a corporate network.
5 |
6 | Many tools of this type work by testing outbound port connections alone, but Egression works by actually uploading a sensitive file to the internet in a number of ways.
7 |
8 | ### Categories
9 | * Network Attacks
10 | * Vulnerability assessment
11 | * Utilities
12 |
13 |
14 | ### Black Hat sessions
15 | [](https://www.blackhat.com/us-17/arsenal/schedule/index.html)
16 |
17 |
18 | ### Code
19 | https://github.com/danielmiessler/egression
20 |
21 |
22 | ### Lead Developer
23 | * Daniel Miessler [@danielmiessler] - https://github.com/danielmiessler
24 |
25 |
26 | ### Social Media
27 | * [Website](https://danielmiessler.com/)
28 | * [Twitter](https://twitter.com/danielmiessler)
29 | * [Podcast](https://danielmiessler.com/podcast/)
30 | * [Linkedin](www.linkedin.com/in/danielmiessler)
31 |
--------------------------------------------------------------------------------
/network_attacks/flashlight.md:
--------------------------------------------------------------------------------
1 | # Flashlight
2 |
3 | ### Description
4 | Pentesters spend too much time during information gathering phase. Flashlight (Fener) provides services to scan network/ports and gather information rapidly on target networks. So Flashlight should be the choice to automate discovery step during a penetration test. In this article, usage of Flashligh application will be explained.
5 |
6 |
7 | ### Categories
8 | * Network Attacks
9 |
10 |
11 | ### Black Hat sessions
12 | [](https://www.blackhat.com/us-14/arsenal.html#Alkan)
13 | [](http://www.blackhat.com/us-15/arsenal.html#heybe-pentest-automation-toolkit)
14 |
15 |
16 | ### Code
17 | https://github.com/galkan/flashlight
18 |
19 |
20 | ### Lead Developer
21 | * Gokhan Alkan - https://github.com/galkan
22 |
23 |
24 | ### Social Media
25 | * [Twitter](https://twitter.com/gokhan_alkn)
26 |
--------------------------------------------------------------------------------
/network_attacks/gr-lora.md:
--------------------------------------------------------------------------------
1 | # gr-lora
2 |
3 | ### Description
4 | gr-lora is an open-source GNU Radio/Software Defined Radio implementation of the LoRa radio physical layer, as derived from the author's black box analysis of the protocol. gr-lora empowers developers and security researchers to think beyond packet sniffing and injection by exposing LoRa's physical layer in software.
5 |
6 | LoRa is a wireless networking technology that can be thought of as high-endurance cellular for IoT and embedded devices. It utilizes a unique Chirp Spread Spectrum modulation and layered encoding scheme to achieve remarkable range while remaining frugal on power.
7 |
8 | PHYs have long been taken for granted, however research such as Travis Goodspeed's packet-in-packet and Dartmouth/River Loop Security's 802.15.4 chipset fingerprinting have demonstrated that physical layer abuse can have severe consequences further up the stack. As a closed protocol, LoRa has only been exposed via layer 2+ interfaces; thus security researchers and developers have lacked the necessary tools to audit and analyze the security and robustness of its PHY.
9 |
10 | With its flexible and open architecture, gr-lora gives security researchers the capability required to explore this nascent protocol from its most fundamental layer.
11 |
12 | For more information on the LoRa PHY and Matt's blind signal analysis process:
13 | * 33c3 Video: https://media.ccc.de/v/33c3-7945-decoding_the_lora_phy
14 | * PoC||GTFO 0x13: https://www.alchemistowl.org/pocorgtfo/pocorgtfo13.pdf
15 |
16 | ### Categories
17 | * Network Attacks
18 | * Wireless
19 | * Reverse Engineering
20 | * Hardware/IoT
21 |
22 | ### Black Hat sessions
23 | [](https://www.blackhat.com/us-17/arsenal/schedule/index.html#gr-lora-an-open-source-sdr-implementation-of-the-lora-phy-8045)
24 |
25 | ### Code
26 | https://github.com/BastilleResearch/gr-lora
27 |
28 | ### Lead Developer
29 | Matt Knight - https://github.com/matt-knight
30 |
31 | ### Social Media
32 | * [Twitter](https://twitter.com/embeddedsec)
33 | * [Company Website](https://bastille.net)
34 |
35 | ----
36 |
37 |
--------------------------------------------------------------------------------
/network_attacks/yasuo.md:
--------------------------------------------------------------------------------
1 | # Yasuo
2 |
3 | ### Description
4 | Yasuo is a ruby script that scans for vulnerable 3rd-party web applications.
5 |
6 | While working on a network security assessment (internal, external, red team gigs etc.), we often come across vulnerable 3rd-party web applications or web front-ends that allow us to compromise the remote server by exploiting publicly known vulnerabilities. Some of the common & favorite applications are Apache Tomcat administrative interface, JBoss jmx-console, Hudson Jenkins and so on.
7 |
8 | If you search through Exploit-db, there are over 10,000 remotely exploitable vulnerabilities that exist in tons of web applications/front-ends and could allow an attacker to completely compromise the back-end server. These vulnerabilities range from RCE to malicious file uploads to SQL injection to RFI/LFI etc.
9 |
10 | Yasuo is built to quickly scan the network for such vulnerable applications thus serving pwnable targets on a silver platter.
11 |
12 | ### Categories
13 | * Network Attacks
14 | * Vulnerability assessment
15 | * Frameworks
16 |
17 |
18 | ### Black Hat sessions
19 | [](https://www.blackhat.com/eu-16/arsenal.html)
20 | [](https://www.blackhat.com/us-17/arsenal/schedule/index.html#yasuo-7909)
21 |
22 |
23 | ### Code
24 | https://github.com/0xsauby/yasuo
25 |
26 |
27 | ### Lead Developer
28 | * Saurabh Harit [0xsauby] - https://github.com/0xsauby
29 |
30 |
31 | ### Social Media
32 | * [Twitter](https://twitter.com/0xsauby)
33 | * [Linkedin](https://www.linkedin.com/in/saurabhharit/)
34 |
--------------------------------------------------------------------------------
/network_defense/lulu.md:
--------------------------------------------------------------------------------
1 | # LuLu
2 |
3 | ### Description
4 | LuLu is the free open-source macOS firewall that aims to block unauthorized (outgoing) network traffic.
5 | 
6 |
7 | Full details and usage instructions can be found [here](https://objective-see.com/products/lulu.html).
8 |
9 |
10 | ### Categories
11 | * Network Defense
12 | * Malware Research
13 |
14 |
15 | ### Black Hat sessions
16 | [](http://www.toolswatch.org/2017/06/the-black-hat-arsenal-usa-2017-phenomenal-line-up-announced/)
17 |
18 | ### Code
19 | https://github.com/objective-see/LuLu
20 |
21 | ### Lead Developer
22 | Patrick Wardle - Objective-See
23 |
24 | ### Social Media
25 | * [Twitter](https://twitter.com/patrickwardle)
26 | * [Company Website](https://objective-see.com)
27 |
28 |
--------------------------------------------------------------------------------
/network_defense/sitch.md:
--------------------------------------------------------------------------------
1 | # SITCH
2 |
3 | ### Description
4 |
5 | SITCH is a distributed cellular anomaly detection and countersurveillance platform.
6 |
7 | SITCH is comprised of a number of sensors and a central service. Sensors are made from easily sourced hardware, and the cost of required components is around $150 each. All information produced by the sensors is aggregated in the service, which handles alerting and data retention.
8 |
9 | Slides and supporting assets from the Black Hat Arsenal talk can be found [here](https://github.com/sitch-io/blackhat_arsenal_2017).
10 |
11 | ### Categories
12 |
13 | * Network Defense
14 |
15 | ### Black Hat sessions
16 |
17 | [](http://www.toolswatch.org/2017/06/the-black-hat-arsenal-usa-2017-phenomenal-line-up-announced/)
18 |
19 | ### Code
20 |
21 | https://github.com/sitch-io
22 |
23 | ### Lead Developer
24 |
25 | Ash Wilson - https://github.com/ashmastaflash
26 |
27 | ### Social Media
28 |
29 | * [Twitter](https://twitter.com/sitch_io)
30 | * [Project Website](https://sitch.io/)
31 |
--------------------------------------------------------------------------------
/network_defense/sweetsecurity.md:
--------------------------------------------------------------------------------
1 | # Sweet Security
2 |
3 | ### Description
4 | Sweet Security is a suite of tools which allows users to monitor local network traffic from a single device as small as a raspberry pi.
5 |
6 | __Client/Sensor__
7 | - Bro IDS to monitor network traffic
8 | - (Optional) Critical Stack Intel to add threat intelligence feeds into Bro
9 | - Logstash to collect and normalize all Bro logs
10 | - Sweet Security code to scan the network and ARP spoof all local network traffic through the device
11 |
12 | __Server__
13 | - Elasticsearch to store logstash and sweet security data
14 | - Kibana to visualize logs/data
15 | - Sweet Security code to search log data for interesting events
16 | - Apache/Flask web app to manage environment
17 |
18 | * More information can be found in the Sweet Security wiki on the Github repository.
19 | * Slides from the public presentations are available on the Github repository.
20 |
21 | ### Categories
22 | * Network Defense
23 | * Forensics
24 | * Incident Response
25 |
26 |
27 | ### Black Hat sessions
28 | [](https://www.toolswatch.org/2017/06/the-black-hat-arsenal-usa-2017-phenomenal-line-up-announced/)
29 |
30 |
31 | ### Code
32 | https://github.com/travisfsmith/sweetsecurity
33 |
34 | ### Lead Developer
35 | Travis Smith
36 |
37 | ### Social Media
38 | * [Twitter](https://twitter.com/mrtrav)
39 | ----
40 |
41 |
42 |
43 |
--------------------------------------------------------------------------------
/network_defense/zenected.md:
--------------------------------------------------------------------------------
1 | # Zenected Threat Defense VPN
2 |
3 | ### Description
4 | __Zenected__ is a cloud based security threat protection service. It’s delivered through a set of pre-configured services. Once a user connects to the __Zenected__, that user’s network traffic is filtered to keep the bad things out (e.g. phishing sites, malware). The only thing this a user has to configure on the endpoint device (be it a mobile device, a desktop or laptop or IoT device) is a VPN connection.
5 |
6 | All services are updated every hour with a new set of threat indicators prepared by Perun Works.
7 |
8 | __Zenected__ is easy to manage. It uses a web front-end for administrators to manage your instance. An administrator user can:
9 | - manage __Zenected__ users including adding more admin users
10 | - blacklist URLs or domain names that you don't want your users to access
11 | - whitelist URLs or domain names, that were identified as malicious but you still want your users to be able to get to them
12 | - review exception requests from users
13 |
14 | If you are a __Zenected__ end-user what you will like about it, is:
15 | - no need to install additional software on your mobile phone, tablet or laptop – __Zenected__ uses standard OS features build-in into all modern systems
16 | - if you encounter a certain resource blocked by the system, you can request an exception. Each exception is then reviewed by an administrator.
17 |
18 | For more info and resources visit: https://zenected.com
19 |
20 | ### Categories
21 | * Network Defense
22 | * Hardening
23 |
24 |
25 | ### Black Hat sessions
26 | [](https://www.toolswatch.org/2017/02/the-black-hat-arsenal-asia-2017-great-line-up/)
27 |
28 |
29 | ### Code
30 | https://github.com/perunworks/zenected
31 |
32 | ### Lead Developer
33 | Tomasz Jakubowski @ Perun Works https://github.com/perunworks
34 |
35 | ### Social Media
36 | * [Twitter](https://twitter.com/perunhimself)
37 | * [Facebook](https://www.facebook.com/Perun-Works-1605484713040277/)
38 | * [LinkedIn](https://www.linkedin.com/company-beta/10580623/)
39 | * [Company Website](https://www.perunworks.com/)
40 | ----
41 |
42 |
43 |
44 |
--------------------------------------------------------------------------------
/osint/.keep:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/whid-injector/blackhat-arsenal-tools/ef013459fd21b22ff63bd9c9a351d30389c47e4a/osint/.keep
--------------------------------------------------------------------------------
/osint/datasploit.md:
--------------------------------------------------------------------------------
1 | # DataSploit - OSINT Framework
2 |
3 | [](http://www.toolswatch.org/2017/02/2016-top-security-tools-as-voted-by-toolswatch-org-readers/)
4 |
5 | ### Description
6 | An #OSINT Framework to perform various recon techniques, aggregate all the raw data, and give data in multiple formats.
7 |
8 | ### Code
9 | https://github.com/datasploit/datasploit
10 |
11 | # Overview of the tool:
12 | * Performs OSINT on a domain / email / username / phone and find out information from different sources.
13 | * Correlates and collaborate the results, show them in a consolidated manner.
14 | * Tries to find out credentials, api-keys, tokens, subdomains, domain history, legacy portals, etc. related to the target.
15 | * Use specific script / launch automated OSINT for consolidated data.
16 | * Performs Active Scans on collected data.
17 | * Generates HTML, JSON reports along with text files.
18 |
19 | ### Categories
20 | * Open Source Intelligence
21 | * Penetration Testing
22 | * Threat Intelligence
23 |
24 | ### Presented At:
25 | [DEFCON 25 ReconVillage](http://reconvillage.org/)
26 |
27 | [DEFCON 24 Demolabs](https://www.defcon.org/html/defcon-24/dc-24-demolabs.html)
28 |
29 | [](http://www.toolswatch.org/2017/09/black-hat-arsenal-europe-2017-lineup/) - EUROPE
30 |
31 | [](http://www.toolswatch.org/2017/06/the-black-hat-arsenal-usa-2017-phenomenal-line-up-announced/) - USA
32 |
33 | [](http://www.toolswatch.org/2017/02/the-black-hat-arsenal-asia-2017-great-line-up/) - ASIA
34 |
35 | [](http://www.toolswatch.org/2016/09/the-black-hat-arsenal-europe-2016-line-up/) - EUROPE
36 |
37 | [](http://www.toolswatch.org/2016/06/the-black-hat-arsenal-usa-2016-remarkable-line-up/) - USA
38 |
39 | ### Documentation
40 | https://datasploit.github.io/datasploit/
41 |
42 | ### Lead Developers
43 | * Shubham Mittal - https://github.com/upgoingstar
44 | * Sudhanshu Chauhan - https://github.com/sudhanshu_c
45 | * Kunal Aggarwal - https://github.com/aggkunal
46 |
47 | ### Social Media
48 | * [Official Website](https://datasploit.github.io/datasploit/)
49 | * [Twitter](https://twitter.com/datasploit)
50 | * [Facebook](https://facebook.com/datasploit)
--------------------------------------------------------------------------------
/phishing/spf.md:
--------------------------------------------------------------------------------
1 | # SPF - SpeedPhishing Framework
2 |
3 | ### Description
4 | SPF (SpeedPhish Framework) is a python tool designed to allow for quick recon and deployment of simple social engineering phishing exercises.
5 |
6 | ### Categories
7 | * Phishing
8 | * Frameworks
9 |
10 | ### Black Hat sessions
11 | [](https://www.toolswatch.org/2015/06/black-hat-arsenal-usa-2015-speakers-lineup/)
12 |
13 | ### Code
14 | https://github.com/tatanus/SPF
15 |
16 | ### Lead Developer
17 | Adam Compton - https://github.com/tatanus
18 |
19 | ### Social Media
20 | * [Twitter](https://twitter.com/tatanus)
21 |
--------------------------------------------------------------------------------
/red_team/legion.md:
--------------------------------------------------------------------------------
1 | # Legion
2 |
3 | ### Description
4 | At its core, Legion is a distributed computing application. It is written in python and designed from the ground up to fulfill various IT related needs. Whether you need a way to logically distribute large or complex commands across multiple systems, or if you need a way to remotely administer 1 or more other systems, Legion can help. Legion goes beyond a typical Master/Manager/Slave architecture and makes use of a MeshNetworking approach to help to dynamically route around failed nodes and networking issues. Additionally, it has the ability to allow remote shell access to any node as well as send individual commands to 1 or all of the nodes within the mesh. And of course all the communications are encrypted between the nodes.
5 |
6 | ### Categories
7 | * Red Team
8 |
9 | ### Black Hat sessions
10 | [](http://www.toolswatch.org/2017/06/the-black-hat-arsenal-usa-2017-phenomenal-line-up-announced/)
11 |
12 | ### Code
13 | https://github.com/MooseDojo/Legion
14 |
15 | ### Lead Developers
16 | * Adam Compton - https://github.com/tatanus https://github.com/MooseDojo
17 | * Bill Harshbarger - https://github.com/bharshbarger https://github.com/MooseDojo
18 |
19 | ### Social Media
20 | * [Twitter](https://twitter.com/tatanus)
21 |
--------------------------------------------------------------------------------
/red_team/shinobot.md:
--------------------------------------------------------------------------------
1 | # ShinoBOT Family
2 |
3 | ### Description
4 | ShinoBOT Family is a malware set to test the security solution / security posture of the organization.
5 |
6 | #### [ShinoBOT](https://shinobot.com)
7 | Backdoor simulator
8 | * customizable on-the-fly
9 | * C&C as a service
10 | * domain randomize (DGA)
11 | * command template
12 |
13 | #### [ShinoBOT Suite](http://shinosec.com/shinobotsuite/)
14 | APT simulator to perform a full scenario
15 | * the ShinoBOT embedded in the JPG file
16 | * decoy file
17 | * downloader / dropper
18 | * shortcut attack
19 |
20 | #### [ShinoLocker](http://shinolocker.com/)
21 | Ransomware Simulator
22 | * AES 128bit
23 | * Free key exchange (no BitCoin to decrypt the file)
24 | * customizable
25 |
26 | #### [ShinoBOT.ps1](http://shinobotps1.com/)
27 | * ShinoBOT powershell edition
28 | * "Fileless" malware
29 |
30 | ### Categories
31 | * Penetration Testing / Red Team
32 |
33 | ### Black Hat sessions
34 |
35 | [](https://www.toolswatch.org/2013/06/announcement-blackhat-arsenal-usa-2013-selected-tools/)
36 | [](https://www.toolswatch.org/2014/06/black-hat-usa-2014-arsenal-tools-speaker-list/)
37 | [](https://www.toolswatch.org/2015/03/black-hat-asia-2015-arsenal-speaker-list/)
38 | [](https://www.toolswatch.org/2015/06/black-hat-arsenal-usa-2015-speakers-lineup/)
39 | [](https://www.toolswatch.org/2016/06/the-black-hat-arsenal-usa-2016-remarkable-line-up/)
40 | [](https://www.toolswatch.org/2016/03/black-hat-arsenal-asia-2016-speakers-line-up/)
41 |
42 | ### Code
43 | https://github.com/Sh1n0g1/ShinoBOT
44 |
45 | ### Lead Developer(s)
46 | Shota Shinogi (@Sh1n0g1)
47 |
48 | ### Social Media
49 | * [Twitter](https://twitter.com/Sh1n0g1)
50 |
51 |
52 |
53 |
--------------------------------------------------------------------------------
/red_team/warberrypi.md:
--------------------------------------------------------------------------------
1 | # WarBerryPi
2 |
3 | ### Description
4 | WarBerryPi was built to be used as a hardware implant during red teaming scenarios where we want to obtain as much information as possible in a short period of time with being as stealth as possible. Just find a network port and plug it in. The scripts have been designed in a way that the approach is targeted to avoid noise in the network that could lead to detection and to be as efficient as possible. The WarBerry script is a collection of scanning tools put together to provide that functionality.
5 |
6 | ### Categories
7 | * Red Teaming
8 | * Hardware Implant
9 |
10 | ### Black Hat sessions
11 |
12 | [](https://www.toolswatch.org/2016/06/the-black-hat-arsenal-usa-2016-remarkable-line-up/)
13 | [](https://www.toolswatch.org/2016/09/the-black-hat-arsenal-europe-2016-line-up/)
14 |
15 | ### Popularity
16 |
17 | [](https://www.toolswatch.org/2017/02/2016-top-security-tools-as-voted-by-toolswatch-org-readers/)
18 |
19 | ### Code
20 | https://github.com/secgroundzero/warberry
21 |
22 | ### Lead Developer
23 | Yiannis Ioannides - https://github.com/secgroundzero/warberry
24 |
25 | ### Social Media
26 | * [Twitter](https://twitter.com/sec_groundzero)
27 |
--------------------------------------------------------------------------------
/reverse_engineering/.keep:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/whid-injector/blackhat-arsenal-tools/ef013459fd21b22ff63bd9c9a351d30389c47e4a/reverse_engineering/.keep
--------------------------------------------------------------------------------
/tool_template.md:
--------------------------------------------------------------------------------
1 | **THIS IS A SAMPLE. MODIFY THE INFORMATION TO REFLECT YOUR TOOL. HEY, REMOVE THIS WARNING BEFORE SUBMISSION**
2 |
3 | # Lynis
4 |
5 | ### Description
6 | Lynis is a security auditing for UNIX derivatives like Linux, macOS, BSD, and others. It performs an in-depth security scan and runs on the system itself. The primary goal is to test security defenses and provide tips for further system hardening. It will also scan for general system information, vulnerable software packages, and possible configuration issues. Lynis was commonly used by people in the "blue team" to assess the security defenses of their systems. Nowadays, penetration testers also have Lynis in their toolkit.
7 |
8 | ### Categories
9 | * Hardening
10 | * Vulnerability assessment
11 |
12 | ### Black Hat sessions
13 | Insert your badge.
14 |
15 | Example:
16 |
17 | [](https://www.toolswatch.org/2014/09/lineup-for-the-blackhat-arsenal-europe-2014/)
18 | [](https://www.toolswatch.org/2015/06/black-hat-arsenal-usa-2015-speakers-lineup/)
19 |
20 | Check the valid links and badges in **badge**
21 |
22 | ### Popularity
23 |
24 | ToolsWatch Annual Best Free/Open Source Security Tool Survey:
25 |
26 | [](https://www.toolswatch.org/2013/12/2013-top-security-tools-as-voted-by-toolswatch-org-readers)
27 | [](https://www.toolswatch.org/2015/01/2014-top-security-tools-as-voted-by-toolswatch-org-readers)
28 | [](https://www.toolswatch.org/2016/02/2015-top-security-tools-as-voted-by-toolswatch-org-readers)
29 | [](https://www.toolswatch.org/2017/02/2016-top-security-tools-as-voted-by-toolswatch-org-readers)
30 |
31 | Check the valid links and badges in **badge**
32 |
33 | ### Code
34 | https://github.com/CISOfy/lynis
35 |
36 | ### Lead Developer(s)
37 | Michael Boelen - Cisofy https://github.com/CISOfy
38 |
39 | ### Social Media
40 | * [Twitter](https://twitter.com/mboelen)
41 | * [Company Website](https://cisofy.com/)
42 | ----
43 |
44 |
45 | ### Badge
46 | #### Arsenal
47 | Once the links and badges selected. You can remove this section Badge before submission.
48 |
49 | * 2011:
50 | * badge: https://rawgit.com/toolswatch/badges/master/arsenal/2011.svg
51 | * USA Session: https://www.toolswatch.org/blackhat-arsenal-us-2011-archive/
52 |
53 | * 2012:
54 | * badge: https://rawgit.com/toolswatch/badges/master/arsenal/2012.svg
55 | * USA Session: https://www.toolswatch.org/blackhat-arsenal-us-2012-archive/
56 | * Europe Session: https://www.toolswatch.org/blackhat-arsenal-europe-2012/
57 |
58 | * 2013:
59 | * badge: https://rawgit.com/toolswatch/badges/master/arsenal/2013.svg
60 | * USA Session: https://www.toolswatch.org/2013/06/announcement-blackhat-arsenal-usa-2013-selected-tools/
61 | * Europe Session: https://www.toolswatch.org/2013/02/selected-tools-for-blackhat-arsenal-europe-2013/
62 |
63 | * 2014:
64 | * badge: https://rawgit.com/toolswatch/badges/master/arsenal/2014.svg
65 | * USA Session: https://www.toolswatch.org/2014/06/black-hat-usa-2014-arsenal-tools-speaker-list/
66 | * Europe Session: https://www.toolswatch.org/2014/09/lineup-for-the-blackhat-arsenal-europe-2014/
67 |
68 | * 2015:
69 | * badge: https://rawgit.com/toolswatch/badges/master/arsenal/2015.svg
70 | * USA Session: https://www.toolswatch.org/2015/06/black-hat-arsenal-usa-2015-speakers-lineup/
71 | * Europe Session: https://www.toolswatch.org/2015/10/black-hat-arsenal-europe-2015-line-up/
72 | * Asia Session: https://www.toolswatch.org/2015/03/black-hat-asia-2015-arsenal-speaker-list/
73 |
74 | * 2016:
75 | * badge: https://rawgit.com/toolswatch/badges/master/arsenal/2016.svg
76 | * USA Session: https://www.toolswatch.org/2016/06/the-black-hat-arsenal-usa-2016-remarkable-line-up/
77 | * Europe Session: https://www.toolswatch.org/2016/09/the-black-hat-arsenal-europe-2016-line-up/
78 | * Asia Session: https://www.toolswatch.org/2016/03/black-hat-arsenal-asia-2016-speakers-line-up/
79 |
80 | * 2017:
81 | * badge: https://rawgit.com/toolswatch/badges/master/arsenal/2017.svg
82 | * Asia Session: https://www.toolswatch.org/2017/02/the-black-hat-arsenal-asia-2017-great-line-up/
83 | * USA Session: http://www.toolswatch.org/2017/06/the-black-hat-arsenal-usa-2017-phenomenal-line-up-announced/
84 |
85 | #### ToolsWatch Survey
86 |
87 | * 2013:
88 | * link: https://www.toolswatch.org/2013/12/2013-top-security-tools-as-voted-by-toolswatch-org-readers/
89 | * badge: https://github.com/toolswatch/badges/blob/master/toptools/2013.svg
90 |
91 | * 2014:
92 | * link: https://www.toolswatch.org/2015/01/2014-top-security-tools-as-voted-by-toolswatch-org-readers/
93 | * badge: https://github.com/toolswatch/badges/blob/master/toptools/2014.svg
94 |
95 | * 2015:
96 | * link: https://www.toolswatch.org/2016/02/2015-top-security-tools-as-voted-by-toolswatch-org-readers/
97 | * badge: https://github.com/toolswatch/badges/blob/master/toptools/2015.svg
98 |
99 | * 2016:
100 | * link: https://www.toolswatch.org/2017/02/2016-top-security-tools-as-voted-by-toolswatch-org-readers/
101 | * badge: https://github.com/toolswatch/badges/blob/master/toptools/2016.svg
102 |
103 | If your tool was ranked 1st, consider using the following badges:
104 |
105 | * 2013:
106 | * badge: https://github.com/toolswatch/badges/blob/master/toptools/rank1_2013.svg
107 |
108 | * 2014:
109 | * badge: https://github.com/toolswatch/badges/blob/master/toptools/rank1_2014.svg
110 |
111 | * 2015:
112 | * badge: https://github.com/toolswatch/badges/blob/master/toptools/rank1_2015.svg
113 |
114 | * 2016:
115 | * badge: https://github.com/toolswatch/badges/blob/master/toptools/rank1_2016.svg
116 |
--------------------------------------------------------------------------------
/vulnerability_assessment/apt2.md:
--------------------------------------------------------------------------------
1 |
2 | # APT2 - An Automated Penetration Testing Toolkit
3 |
4 | ### Description
5 | ```
6 | dM. `MMMMMMMb. MMMMMMMMMM
7 | ,MMb MM `Mb / MM \
8 | d'YM. MM MM MM ____
9 | ,P `Mb MM MM MM 6MMMMb
10 | d' YM. MM .M9 MM MM' `Mb
11 | ,P `Mb MMMMMMM9' MM ,MM
12 | d' YM. MM MM ,MM'
13 | ,MMMMMMMMb MM MM ,M'
14 | d' YM. MM MM ,M'
15 | _dM_ _dMM_MM_ _MM_MMMMMMMM
16 |
17 |
18 | An Automated Penetration Testing Toolkit
19 | ```
20 | This tool will perform an NMap scan, or import the results of a scan from Nexpose, Nessus, or NMap. The processesd results will be used to launch exploit and enumeration modules according to the configurable Safe Level and enumerated service information.
21 |
22 | All module results are stored on localhost and are part of APT2's Knowledge Base (KB). The KB is accessible from within the application and allows the user to view the harvested results of an exploit module.
23 |
24 | ### Categories
25 | * Vulnerability assessment
26 | * Exploitation
27 | * Frameworks
28 |
29 | ### Black Hat sessions
30 | [](https://www.toolswatch.org/2016/06/the-black-hat-arsenal-usa-2016-remarkable-line-up/)
31 | [](https://www.toolswatch.org/2016/09/the-black-hat-arsenal-europe-2016-line-up/)
32 |
33 | ### Code
34 | https://github.com/MooseDojo/apt2
35 |
36 | ### Main developer
37 | * Adam Compton - https://github.com/tatanus https://github.com/MooseDojo
38 | * Austin Lane - https://github.com/MooseDojo
39 |
40 | ### Social Media
41 | * [Twitter](https://twitter.com/tatanus)
42 | * [Twitter](https://twitter.com/capndan)
43 |
--------------------------------------------------------------------------------
/webapp_security/jack.md:
--------------------------------------------------------------------------------
1 | # Jack
2 |
3 | ### Description
4 | Jack is a web based ClickJacking PoC development assistance tool.
5 | Jack makes use of static HTML and JavaScript to create a drag n drop environment to illustrate the impact of ClickJacking.
6 |
7 | ### Categories
8 | * Webb Application Security
9 | * Vulnerability assessment
10 | * Phishing
11 |
12 | ### Black Hat sessions
13 | []( https://www.toolswatch.org/2015/10/black-hat-arsenal-europe-2015-line-up/)
14 |
15 | ### Code
16 | https://github.com/sensepost/jack
17 |
18 | ### Lead Developer
19 | Chris Le Roy - SensePost https://github.com/sensepost
20 |
21 | ### Social Media
22 | * [Twitter](https://twitter.com/brompwnie)
23 | * [Company Website](https://sensepost.com/)
24 | ----
25 |
--------------------------------------------------------------------------------
/webapp_security/owtf.md:
--------------------------------------------------------------------------------
1 | # OWASP Offensive Web Testing Framework (OWTF)
2 |
3 | ### Description
4 | OWASP OWTF is a project focused on penetration testing efficiency and alignment of security tests to security standards like the OWASP Testing Guide (v3 and v4), the OWASP Top 10, PTES and NIST so that pentesters will have more time to:
5 |
6 | * See the big picture and think out of the box
7 | * More efficiently find, verify and combine vulnerabilities
8 | * Have time to investigate complex vulnerabilities like business logic/architectural flaws, etc.
9 | * Perform more tactical/targeted fuzzing on seemingly risky areas
10 | * Demonstrate true impact despite the short timeframes we are typically given to test
11 |
12 | OWTF includes:
13 | * A highly configurable plugin system
14 | * A fast (the fastest Python MiTM proxy yet!) MiTM SSL proxy
15 | * A pretty web interface
16 | * An interactive report
17 | * Full coverage for OWASP Testing Guide v3/v4, PTES, NIST, and CWE mappings
18 | * Built-in integrations for Mozilla Zest and Plug-n-Hack standards
19 | * REST API exposed to control and extend the functionality of OWTF
20 |
21 | ### Categories
22 |
23 | * Web Application
24 | * OWASP
25 | * Pentest
26 | * Vulnerability assessment
27 |
28 | ### Black Hat sessions
29 |
30 | [](http://www.toolswatch.org/2017/06/the-black-hat-arsenal-usa-2017-phenomenal-line-up-announced/)
31 |
32 | ### Code
33 | https://github.com/owtf/owtf
34 |
35 | ### Lead Developers
36 |
37 | - Abraham Aranguren (https://twitter.com/7a_)
38 | - Bharadwaj Machiraju (https://twitter.com/tunnelshade_)
39 | - Viyat Bhalodia (https://twitter.com/viyat)
40 |
41 |
42 | ### Social Media
43 |
44 | * [Twitter](https://twitter.com/owtfp)
45 | * [Project homepage](http://owtf.github.io/)
46 | * [IRC](http://webchat.freenode.net/?randomnick=1&channels=%23owtf&prompt=1&uio=MTE9MjM20f)
47 | * [Wiki](https://www.owasp.org/index.php/OWASP_OWTF)
48 | * [Slack](https://owasp.herokuapp.com) and join channel `#project-owtf`
49 | * [User Documentation](http://docs.owtf.org/en/latest/)
50 | * [Youtube channel](https://www.youtube.com/user/owtfproject)
51 | * [Slideshare](http://www.slideshare.net/abrahamaranguren/presentations)
52 | * [Blog](http://blog.7-a.org/search/label/OWTF)
53 |
54 |
--------------------------------------------------------------------------------
/webapp_security/wssat.md:
--------------------------------------------------------------------------------
1 |
2 |
3 | # WSSAT - Web Service Security Assessment Tool
4 |
5 | ### Description
6 | WSSAT is an open source web service security scanning tool which provides a dynamic environment to add, update or delete vulnerabilities by just editing its configuration files. This tool accepts WSDL address list as input file and for each service, it performs both static and dynamic tests against the security vulnerabilities. It also makes information disclosure controls.
7 | With this tool, all web services could be analysed at once and the overall security assessment could be seen by the organization.
8 |
9 | **Objectives of WSSAT are to allow organizations:**
10 | * Perform their web services security analysis at once
11 | * See overall security assessment with reports
12 | * Harden their web services
13 |
14 | **WSSAT’s main capabilities include:**
15 |
16 | **Dynamic Testing:**
17 | * Insecure Communication - SSL Not Used
18 | * Unauthenticated Service Method
19 | * Error Based SQL Injection
20 | * Cross Site Scripting
21 | * XML Bomb
22 | * External Entity Attack - XXE
23 | * XPATH Injection
24 | * Verbose SOAP Fault Message
25 |
26 | **Static Analysis:**
27 | * Weak XML Schema: Unbounded Occurrences
28 | * Weak XML Schema: Undefined Namespace
29 | * Weak WS-SecurityPolicy: Insecure Transport
30 | * Weak WS-SecurityPolicy: Insufficient Supporting Token Protection
31 | * Weak WS-SecurityPolicy: Tokens Not Protected
32 |
33 | **Information Leakage:**
34 | * Server or technology information disclosure
35 |
36 | **WSSAT’s main modules are:**
37 | * Parser
38 | * Vulnerabilities Loader
39 | * Analyzer/Attacker
40 | * Logger
41 | * Report Generator
42 |
43 | The main difference of WSSAT is to create a dynamic vulnerability management environment instead of embedding the vulnerabilities into the code.
44 |
45 | _This project has been developed as Term Project at Middle East Technical University (METU), Software Management master program._
46 |
47 | ### Categories
48 |
49 | * Web Application
50 | * Web Service
51 | * Pentest
52 | * Vulnerability assessment
53 |
54 | ### Black Hat sessions
55 |
56 | [](https://www.blackhat.com/us-16/arsenal.html#web-service-security-assessment-tool-wssat) [](https://www.blackhat.com/eu-16/arsenal.html#wssat-web-service-security-assessment-tool)
57 |
58 | ### Code
59 | https://github.com/YalcinYolalan/WSSAT
60 |
61 | ### Lead Developers
62 |
63 | - Mehmet Yalçın YOLALAN (https://www.linkedin.com/in/yalcinyolalan/)
64 | - Salih TALAY (https://www.linkedin.com/in/salih-talay-49025238/)
65 |
66 | ### Social Media
67 |
68 | * [Project homepage](http://yalcinyolalan.github.io/WSSAT/)
69 |
70 |
71 |
--------------------------------------------------------------------------------
/webapp_security/zap.md:
--------------------------------------------------------------------------------
1 | # ZAP
2 |
3 | ### Description
4 |
5 | The OWASP Zed Attack Proxy (ZAP) is one of the world’s most popular free security tools and is actively maintained by hundreds of international volunteers. It can help you automatically find security vulnerabilities in your web applications while you are developing and testing your applications. Its also a great tool for experienced pentesters to use for manual security testing.
6 |
7 | Some of the built in features include: Intercepting proxy server, Traditional and AJAX Web crawlers, Automated scanner, Passive scanner, Forced browsing, Fuzzer, WebSocket support, Scripting languages, and Plug-n-Hack support. It has a plugin-based architecture and an online ‘marketplace’ which allows new or updated features to be added. The GUI control panel is easy to use, and the API functions make it ideal for automation testing and continuous assessments in a SDLC.
8 |
9 | ### Categories
10 |
11 | * Web Application
12 | * OWASP
13 | * Pentest
14 | * Web API Security
15 | * Vulnerability assessment
16 |
17 | ### Black Hat sessions
18 |
19 | [](https://www.toolswatch.org/2016/09/the-black-hat-arsenal-europe-2016-line-up/)
20 | [](https://www.toolswatch.org/2014/09/lineup-for-the-blackhat-arsenal-europe-2014/)
21 | [](https://www.toolswatch.org/2014/06/black-hat-usa-2014-arsenal-tools-speaker-list/)
22 |
23 | ### Popularity
24 |
25 | ToolsWatch Annual Best Free/Open Source Security Tool Survey:
26 |
27 | [](https://www.toolswatch.org/2013/12/2013-top-security-tools-as-voted-by-toolswatch-org-readers)
28 | [](https://www.toolswatch.org/2015/01/2014-top-security-tools-as-voted-by-toolswatch-org-readers)
29 | [](https://www.toolswatch.org/2016/02/2015-top-security-tools-as-voted-by-toolswatch-org-readers)
30 | [](https://www.toolswatch.org/2017/02/2016-top-security-tools-as-voted-by-toolswatch-org-readers)
31 |
32 | ### Code
33 |
34 | * [OWASP ZAP](https://github.com/zaproxy/zaproxy)
35 | * [Extensions](https://github.com/zaproxy/zap-extensions)
36 |
37 | ### Lead Developer
38 |
39 | Mozilla \ Simon Bennetts - https://github.com/psiinon
40 |
41 | ### Social Media
42 |
43 | * [Twitter](https://twitter.com/zaproxy)
44 | * [Blog](https://zaproxy.blogspot.co.uk)
45 | * [GitHub](https://github.com/zaproxy)
46 |
47 |
48 |
--------------------------------------------------------------------------------