Responsible Disclosure Policy

We take security very seriously. We would rather hear about a flaw from you than read about it in public. This document tells you what we consider in scope, how to test responsibly, how to reach us, and what happens after you report.

This policy is for both Spooky Services and SpookyKipper services.

1. How to report

I. Advisory form (preferred): https://advisories.spookysrv.com/request

II. By email (preferred if under active exploitation):

If under active exploitation, please prefix the email subject with "INCIDENT" and we will respond as quickly as possible.

Email PGP Keys (Same keys, two repositories):

We treat encrypted and unencrypted reports the same; encryption is welcome, not required.

III. Open Source Projects: For open source projects we maintain, you can also submit reports through GitHub private vulnerability reporting.

IV. Fallbacks:

  1. Through HITCON ZeroDay https://zeroday.hitcon.org/vulnerability/submit
  2. the Discord invite published in our security.txt (https://security.spookysrv.com/.well-known/security.txt).

Please only use the fallbacks if you cannot reach us through the main channels.

Languages: English or Traditional Chinese.

Please include:

  1. Vulnerability type, description, severity, and any relevant CVE/CWE identifiers.
  2. Suggested fix or mitigation, if you have one.
  3. The affected service and exact URL/hostname/component, including the version if known.
  4. Step-by-step reproduction, with a proof of concept (request/response pairs, screenshots, or code).
  5. Your assessment of impact, and whether the flaw is in our code or an upstream component.
    You may want to report to the upstream vendor as well if available.
  6. Your handle if you want public credit.
    Not all reports are eligible for credit, but we will let you know if yours is.
    Low risk reports may not be made public, thus no credit is given for them.
  7. Your preferred disclosure timing/embargo timeframe with a reason on why this time, if you wish to disclose it publicly independently in the future.
  8. Any test accounts or test artifacts you created.
  9. AI usage (prompts, generated code, etc.) if any was used in the process of finding or reproducing the issue.
    We treat AI-assisted reports the same as any other report, but we need to know if AI was used in order to assess the risk of the report and its reproducibility.

2. What is in scope

Spooky Services (spookysrv.com & ssite.link)

Item Domain Notes
Main site spookysrv.com Report to us
Hub hub.spookysrv.com Report to us + *NamelessMC or its module developers
Spooky ID id.spookysrv.com Report to us + Authentik
Single Sign On sso.spookysrv.com Report to us
Advisory site advisories.spookysrv.com Report to us + GPlatform
Flow Backend flow.spookysrv.com Report to us
Flow App app.flow.spookysrv.com & Mobile Apps Report to us
HKTransports API *.hktransports.spookysrv.com Report to us
OTA App Config appconfig.spookysrv.com Report to us
Analytics popsicle.spookysrv.com Report to us + Plausible CE
Uptime Monitor uptime.spookysrv.com Report to us + Uptime Kuma
Server Monitor beszel.spookysrv.com Report to us + Beszel
Email mail.spookysrv.com Report to us + NameCrane + SmarterMail
Email - MTA-STS mta-sts.spookysrv.com Report to us + NameCrane
Email - SMTP spookysrv.com MX records Report to us + NameCrane
Email - Exchange autodiscover.spookysrv.com Report to us + NameCrane
F-Droid Repository repo.spookysrv.com Report to us + *fdroid-store
AltStore Repository repo.spookysrv.com/ios Report to us + GithubStore
Labs lab[s].spookysrv.com Report to us
uMap umap.spookysrv.com Report to us + uMap
Matrix matrix.spookysrv.com Report to us + Conduit
Short Links ssite.link Report to us + shlink
Container Registry ghcr.io/spookyservices/* Report to us
GitHub Projects github.com/SpookyServices/* Report to us
Server Infrastructure yuki/shadowrealm.spookysrv.com Report to us
Others spookysrv.com subdomains Report to us

* We have made considerable amount of modifications to these projects, the issue may lie in our code rather than upstream. Please verify before reporting to upstream. If you are unsure, report to us first and we will help you determine the right place to report.

There is no need to report to upstream if the issue lies within our infrastructure or custom settings.

We may forward your report to the upstream vendor if needed.

Spookhost (spookhost.xyz & spookhost.space)

Item Domain Notes
Main site spookhost.xyz Report to us
Client Portal portal.spookhost.xyz Report to us + *Xera
Control Panel cpanel.spookhost.xyz Report to us + *iFastNet
Documentations docs.spookhost.xyz Report to us
Status Page status.spookhost.xyz Report to us + Uptime Kuma
Server Status Page servers.status.spookhost.xyz Report to us + Upptime
Spookhost Cloud [*.]cloud.spookhost.xyz Report to us + Nextcloud
File Manager filemanager.spookhost.space Report to us + iFastNet
Email mail.spookhost.xyz Report to us + NameCrane + SmarterMail
Email - MTA-STS mta-sts.spookhost.xyz Report to us + NameCrane
Email - SMTP spookhost.xyz MX records Report to us + NameCrane
Email - Exchange autodiscover.spookhost.xyz Report to us + NameCrane
FTP Server ftpupload.net Report to iFastNet + optionally us
Databases sql* Report to iFastNet + optionally us
Softaculous sv1.scriptinstall.rocks Report to iFastNet + optionally us
phpMyAdmin php-myadmin.net Report to iFastNet + optionally us
Site Builder site.pro Report to Site.pro + optionally us
Hosted Websites --- Report to the website owner
Hosted Websites (Infrastructure) --- Report to iFastNet + optionally us
Others spookhost.xyz/space subdomains Report to us

* We have made considerable amount of modifications to these projects, the issue may lie in our code rather than upstream. Please verify before reporting to upstream. If you are unsure, report to us first and we will help you determine the right place to report.

There is no need to report to upstream if the issue lies within our infrastructure or custom settings.

We may forward your report to the upstream vendor if needed.

ListCraft (listcraft.top)

Item Domain Notes
Main site listcraft.top Report to us + *Ultimate Minecraft Server List
Email mail.listcraft.top Report to us + NameCrane + SmarterMail
Email - MTA-STS mta-sts.listcraft.top Report to us + NameCrane
Email - SMTP listcraft.top MX records Report to us + NameCrane
Email - Exchange autodiscover.listcraft.top Report to us + NameCrane
Others listcraft.top subdomains Report to us

* We have made considerable amount of modifications to these projects, the issue may lie in our code rather than upstream. Please verify before reporting to upstream. If you are unsure, report to us first and we will help you determine the right place to report.

There is no need to report to upstream if the issue lies within our infrastructure or custom settings.

We may forward your report to the upstream vendor if needed.

SpookyKipper (spooky.hk)

Item Domain Notes
Main site spooky.hk Report to us
Email mail.spooky.hk Report to us + NameCrane + SmarterMail
Email - MTA-STS mta-sts.spooky.hk Report to us + NameCrane
Email - SMTP spooky.hk MX records Report to us + NameCrane
Email - Exchange autodiscover.spooky.hk Report to us + NameCrane
HK Telecom Info telecom.spooky.hk Report to us
UE Capability Parser [v]uecap.spooky.hk Report to us + UE Capability Parser
Privnote privnote.spooky.hk Report to us + Cryptgeon
LMGTFY search/lmgtfy/g.spooky.hk Report to us
Digital Garden obsidian.spooky.hk Report to us
OpenWebUI chat.spooky.hk Report to us + OpenWebUI
JUPAS Calculator 2027 jupascalc.spooky.hk Report to us
Bio e-z.bio/spookykip Report to E-Z Services + optionally us
Img Share kippy.pp.ua Report to us + E-Z Services
HKTransports github.com/SpookyKipper/HKTransports Report to us
CellularViewer github.com/SpookyKipper/CellularViewer Report to us
ContextualTabGroups github.com/SpookyKipper/ContextualTabGroups Report to us
Other GitHub Projects github.com/SpookyKipper/* Report to us
Others spooky.hk subdomains Report to us

* We have made considerable amount of modifications to these projects, the issue may lie in our code rather than upstream. Please verify before reporting to upstream. If you are unsure, report to us first and we will help you determine the right place to report.

There is no need to report to upstream if the issue lies within our infrastructure or custom settings.

We may forward your report to the upstream vendor if needed.

Email security, worldwide

Reports about spoofing or auth issues on our own sending domains are welcome, though we run SPF hard-fail, DMARC p=reject, and MTA-STS enforcement on all four zones, so there should be little to find.

3. What is out of scope

  • Customer websites hosted on Spookhost. Sites on customer domains (or on customer subdomains of our zones) belong to their owners. Only report them if the flaw is in our platform (the panel, a shared component, cross-tenant isolation etc.).
  • Third-party and vendor components. Upstream bugs in Cloudflare, our shared-hosting vendor, shlink, PHP itself, and similar belong to those vendors. We do accept reports of exploitable configurations of these components in our deployment, and we can help you reach the vendor when the bug lives upstream.
  • Reports with no realistic impact: we generally will not act on brute-force noise against Cloudflare challenge pages, findings from automated scanners unaccompanied by a working proof of concept, or theoretical issues that require conditions you cannot demonstrate.
  • Newly disclosed Zero-Day vulnerabilities in 3rd party software: we need time to patch it, please only report them to us if it is not patched/mitigated after 72 hours of public disclosure.

4. Testing rules

The short version: probe politely, use only accounts you created, and stop the moment you see something you should not be able to see.

  • Test only against accounts, servers, and content that belong to you.
  • Do not access, copy, modify, or exfiltrate other users' data. If you encounter data that clearly is not yours, stop, do not explore further, and tell us the minimum needed to understand the leak.
  • No denial-of-service, no stress testing, no resource exhaustion, and no logging/spamming.
  • Do not use automated vulnerability scanners.
  • Do not attempt challenge-solving at scale or try to knock our rate limits over.
  • No social engineering, phishing, or physical attacks against us, our staff, or our users.
  • Active exploitation ends at a minimal proof of concept. No persistent backdoors, pivoting, and persistence.
  • Revert or delete whatever you changed when you are done.
  • When you are unsure whether something is allowed, ask first; we answer quickly.

5. What happens after you report

We are a small team running free services, so these are commitments we can actually keep, not enterprise SLAs:

Stage Target
Acknowledgement Within 72 hours
Triage and severity rating Within 7 days
Status updates while open At least every 14 days
Coordinated public disclosure After the fix ships, or 90 days after acknowledgement, whichever comes first (we can agree otherwise per report)
  • Accepted issues are fixed and then written up as a public advisory on https://advisories.spookysrv.com, following our normal GAdvisory style. We will tell you when the advisory goes live.
  • When a flaw is upstream (host platform, Cloudflare, a library), we will tell you that honestly and forward it to the vendor; ask us to keep you in the loop and we will.
  • We will not hand your report to a third party without telling you, and we will not misrepresent your role. We may forward your report to the vendor if the flaw is upstream at our own discretion, but we will inform you if we do so.

6. Recognition

  • Accepted and eligible reports earn a named credit (your handle or name, your choice, and a link if you want one) on the published advisory and our thanks on the Advisories site.
  • We do not pay bounties. Our services are free; crediting you publicly is the currency we have.

7. Safe harbor

We will not pursue legal action against anyone who tests in good faith, stays within the scope, respects the rules, and reports promptly. This policy is not an invitation or authorization to access anyone else's data or disrupt service: unless a test falls squarely within this document, ordinary law (including Hong Kong's, where we operate) still applies, so when in doubt, ask.

If you believe you have found a security incident already in progress (someone else exploiting something), skip the form and email [email protected] immediately, prefix "INCIDENT" in the subject.

8. Program details

Copyright © 2026 Spooky Services. All rights reserved.