Skip to content

Security: zis3c/MLBB-CounterDraft

Security

SECURITY.md

Security Policy

Purpose

MLBB CounterDraft is intended for local development and open-source collaboration. Any helper, sync service, or companion process associated with the project should be visible, opt-in, and easy to stop.

Supported scope

Security concerns in this project usually fall into one of these buckets:

  • data exposure
  • command execution
  • sync abuse
  • build or runtime exposure
  • network access broader than expected

How to report

When reporting a security issue, include:

  • the affected file, module, or route
  • whether the issue affects local use, networked use, or both
  • the smallest reliable reproduction steps
  • whether the problem is caused by sync, UI, scoring, or a helper service

Keep the first report minimal. Do not publish exploit details publicly until the issue has been reviewed.

Security expectations

The project should follow these rules:

  • bind network services as tightly as possible
  • require explicit user consent for install or runtime helpers
  • never store secrets in the repository
  • avoid hidden startup or stealth behavior
  • whitelist commands when a helper can trigger actions
  • log meaningful actions when a helper is involved

Not in scope

This repository is not intended to be a stealth tool, a hidden implant, or a remote access package that starts without clear user awareness. If a future helper is added, it should be documented, visible, and removable without friction.

There aren't any published security advisories