Ethics and editorial policy
How we decide what to publish, and what we won't.
Last updated 9 Nov 2026
Offensive security knowledge is dual-use. These rules decide what we publish and how.
What we publish
We publish research that helps defenders understand real attacks: how a technique works, what it looks like in telemetry, and how to prevent or contain it. Each article covers detection and mitigation, not just the attack.
What we don't publish
- Working exploits for unpatched vulnerabilities, or weaponised code aimed at a specific organisation.
- Instructions whose main use is harming people: stalking, account takeover of individuals, fraud or harassment.
- Stolen or leaked personal data, credentials or private communications.
- Research on systems the author was not authorised to test.
Disclosure
When our own research finds a vulnerability, we report it to the vendor first and follow coordinated disclosure, normally 90 days, shorter if it is exploited in the wild. See responsible disclosure for reports about this site.
Accuracy and corrections
Technical claims are reproduced in a lab or sourced. When we get something wrong we correct it in the article and note the change at the end. Send corrections to connect@hackersroot.com.
Sponsorship and affiliate links
Sponsors buy labelled placements, never editorial coverage. Sponsors do not review articles before publication. Where an article contains an affiliate link, we say so next to the link. We only recommend products we would use ourselves.
Contributors
Guest authors must declare conflicts of interest, such as employment by a vendor whose product appears in the article. Declared interests are shown with the byline.
Community
Forum discussions follow the community guidelines. The same limits apply there: no live exploitation of systems you don't own, no personal data, no harassment.