Website information
Security reporting
Report a concern privately and minimise what you disclose initially.
Updated 10 November 2026 · Revision 2026-11-10.1
Reporting route
Use the existing project contact info@sphinixx.co.uk to request an appropriate private reporting channel. Initially describe the affected public page or product and general impact. Do not send passwords, user records, exploit dumps or sensitive attachments.
Testing boundaries
This page does not authorise intrusive testing, access to another person’s data, disruption or bypass of access controls. No bug bounty, legal safe harbour, continuous monitoring or response-time commitment is offered here.
Handling status
For an unrecognised publisher message, read the Windows software notice. If you suspect a tampered file, leave it unopened and include the download URL and any SHA-256 fingerprint in your report.