Grey Hat Statement

[Asphyxia]

Edit: Any CRITICAL harmful/threatening vulnerabilities are not released publicly for safety concerns (depending) --- right now I am in the process of working out a better structure through communication with TeamSpeak developers which is safer for everyone.

As many of you may know, R4P3 is a grey hat community and our security research team operates with grey ethics. We are not afraid to restart a TeamSpeak 3 server instance hundreds of times if it means finding a zero-day. When we do find a zero-day, we are comfortable with either releasing it to the public for free or in our VIP section for subscribed members to inspect and learn from.

Our primary intent is to raise security awareness among the TeamSpeak community and to inspire people to research through education and information. What users do with a harmless PoC (Proof-of-Concept) is not our responsibility and we can only hope they do not have dark intentions.

Gray hat describes a cracker (or, if you prefer, hacker) who exploits a security weakness in a computer system or product in order to bring the weakness to the attention of the owners. Unlike a black hat, a gray hat acts without malicious intent. The goal of a gray hat is to improve system and network security. However, by publicizing a vulnerability, the gray hat may give other crackers the opportunity to exploit it. This differs from the white hat who alerts system owners and vendors of a vulnerability without actually exploiting it in public.

source: http://searchsecurity.techtarget.com/definition/gray-hat

Notice: a gray hat acts without malicious intent.