Security Policy Version: 4.0
Previous Version: 3.0

We actively maintain and provide security updates for the following versions:

If you discover any security vulnerability, please report it responsibly.

• GitHub Issues (Private Disclosure Recommended)
• Facebook Group: BANGLADESH CYBER SQUAD
• Direct Developer Contact (if available)

• Vulnerability type (e.g., RCE, Injection, Logic flaw)
• Steps to reproduce
• Affected module/file
• Proof of Concept (PoC) (if possible)
• Suggested fix (optional but appreciated)

• Core Python launcher (doom-cannon.py)
• Go modules (*.go)
• CLI interaction system
• Input handling system
• Headers / proxy handling

• Third-party libraries
• Misconfigured user environments
• Social engineering attacks
• DDoS misuse complaints

This tool is strictly for:

• Educational purposes
• Security research
• Authorized testing

🚫 STRICTLY PROHIBITED:

• Unauthorized attacks
• Real-world disruption
• Illegal activities

Any misuse is NOT the responsibility of the developers.

Users are advised to:

• Run the tool in controlled environments
• Avoid using real targets without permission
• Keep dependencies updated
• Use VPN / sandbox environments for testing

We appreciate responsible disclosure 🙌

• Valid reports may receive:
  • Public credit
  • Contributor recognition
  • Future collaboration opportunities

• Do NOT publicly disclose vulnerabilities before patch
• Developers reserve the right to delay disclosure until fix is released

Security is a shared responsibility.
Help us improve this project by reporting issues responsibly ❤️