Skip to content

Security: HanSoBored/Android-Mem-Kit

Security

SECURITY.md

Security Policy

Supported Versions

Version Supported
1.0.x

Reporting a Vulnerability

We take security vulnerabilities seriously. If you discover a security issue, please follow these guidelines:

How to Report

  1. DO NOT create a public GitHub issue for security vulnerabilities
  2. DO send a private report to: raihanzxzy@gmail.com
  3. Include as much information as possible:
    • Description of the vulnerability
    • Steps to reproduce
    • Potential impact
    • Suggested fix (if any)

What to Expect

  • Acknowledgment: Within 48 hours
  • Initial Response: Within 7 days
  • Resolution Timeline: 90 days (standard responsible disclosure)

Disclosure Policy

We follow a responsible disclosure process:

  1. Reporter submits vulnerability privately
  2. We acknowledge and assess the report
  3. We work on a fix
  4. Fix is released
  5. Vulnerability is publicly disclosed (after 30 days)

Scope

This security policy applies to:

  • The core library code (include/, src/)
  • Build system (CMakeLists.txt)
  • Official examples

Out of Scope:

  • Dependencies (ShadowHook, XDL) - report to upstream
  • Third-party code

Bug Bounty

Currently, we do not offer bug bounties. However:

  • Contributors will be credited (with permission)
  • Hall of Fame recognition available

Security Best Practices for Users

When using this library:

  1. Only use on authorized systems - Never test apps you don't own or have permission to analyze
  2. Keep dependencies updated - Regularly update ShadowHook and XDL
  3. Follow local laws - Comply with DMCA, CFAA, and local computer misuse laws
  4. Responsible disclosure - Report vulnerabilities found in target apps to their developers

Contact

For security concerns:


Thank you for helping keep Android-Mem-Kit secure!

There aren’t any published security advisories