Secure contact

Send a tip, correction, or inquiry

Send vulnerability context, incident tips, corrections, source material, or editorial inquiries for review. Editorial review and timestamps follow U.S. Eastern Time.

Pick the topic that matches your message — it decides which desk sees it first. News tips and research disclosures reach the editorial team; corrections go to whoever wrote the article. We read everything that arrives and aim to reply to actionable tips and corrections within two business days. Not every message gets a reply, but every correction request does.

Sensitive tips

Avoid sending exploit code, credentials, personal data, or victim-sensitive material through this form. Use the first message to request a safer channel.

What makes a tip usable

Tell us what is affected and how you know. Product and version, the CVE if one exists, whether exploitation is confirmed or suspected, and any advisory or reference we can check. We verify before publishing, so a pointer to a primary source moves a tip along faster than anything else.

Corrections

Include the article URL and the specific claim you are disputing, with supporting context. Our corrections policy is described on the about page.

Advertising

Use the Advertising topic for sponsorship and placement enquiries. Sponsored placements are labelled and never affect editorial coverage — see how this site is funded.