Public sources only
Contributor drafts must cite public advisories, vendor posts, CERT notices, official repositories or named research.
Editorial safety
Editorial standards for HackWatch contributors
HackWatch accepts contributor articles only when they improve reader safety, cite verifiable public sources and avoid operational harm.
No exploit code
Do not publish working exploit code, weaponized instructions, credential theft steps or operational abuse details.
No private victim data
Do not include personal data, private emails, tokens, secrets, logs or screenshots that identify victims unnecessarily.
No fake credentials
Author profiles may list only real, author-approved links and credentials verified by the editor.
Editor approval
Contributor drafts cannot publish directly and must pass editor review before any public release.
Corrections policy
Corrections are reviewed against public evidence and updated in the article instead of hidden or duplicated.
Article review checklist
- Lead answers who, what, when, where and why it matters.
- Primary sources are linked before derivative summaries.
- Claims are separated from confirmed facts.
- Defensive actions are practical and safe for readers.
- AI-generic wording is rewritten with specific evidence, timelines and context.
- Images, screenshots and examples remove secrets and private victim details.
Correction path
Send correction requests to [email protected] with the article URL, the exact claim, the requested correction and supporting public evidence.