Wired doesn't cover "Russia" as a mood. It covers Russia as a mechanism — infrastructure, code, supply chains, and the people who operate them.

That distinction is the entire pitch. Lead with the artifact, not the geopolitics.

The beat spans state-linked hacking, disinformation operations, sanctions evasion, surveillance tech, and the grey-market hardware moving across borders.

Wired Things Russian reporters want the technical proof: the leaked contract, the firmware version, the Telegram channel, the procurement invoice.

They do not want a think-tank essay on multipolarity. Analysis is table stakes; documentation is the story.

Your directory shows 2+ active bylines, with Matthew Champion and Tim Marchman as representative writers.

Use them as entry points, not as a fixed map. Wired's national security and tech desks share the beat, so a strong artifact-driven pitch can travel between them.

Before sending, verify recency: open the writer's last five pieces and confirm the beat overlap this month.

Build the Wired Things Russian reporters list as a living document — byline date, angle, source type, and whether the piece depended on documents or interviews.

Signals a writer is currently active on the beat:

• Byline within the last 30 days on Russia, hacking, or disinformation.
• Recent follows or engagement with security researchers and OSINT accounts.
• Repeated sourcing from court documents, DOJ/OFAC filings, or vendor threat reports.
• Co-bylines with the security desk — a sign of cross-desk appetite.

Wired Things Russian journalists reward specificity. One verifiable detail outperforms three paragraphs of context.

Strong angles cluster around: state-aligned ransomware crews and their affiliates, sanctions-evasion logistics, drone and EW hardware supply chains, Telegram as an operational platform, and propaganda-for-hire ecosystems.

Weak angles: policy prognostication, "expert warns" scolding, and anything that reads like a press release with "Russia" inserted.

What to attach in the first email:

• One-line headline.
• The single hardest piece of evidence you hold.
• Why it's exclusive or first.
• The named human at the center of it.
• What you can deliver within 48 hours.

Ethical guardrail: be explicit about provenance. Wired will not launder state-produced material, and neither should your pitch.

Flag disinformation risk yourself — it builds credibility fast.

Email is the channel. DMs are for warm follow-ups, not first contact.

Keep the subject line factual and artifact-forward: "Leaked procurement docs: Russian drone maker's Shenzhen supply chain."

Avoid attachments on first contact. Describe the document, offer to share on request.

For Wired Things Russian journalists contacts, route through the outlet's standard editorial address if you lack a direct line — but name the writer in the first line so it gets routed correctly.

Follow-up cadence: one nudge at 72 hours, one at seven days, then stop. Silence is a pass.

Never CC multiple writers on the same pitch. Choose one owner and note in the email that it's exclusive to them.

• The story is about a mechanism, not a geopolitical vibe.
• I have at least one verifiable artifact (document, log, invoice, domain record).
• The pitch names a specific human or organization at the center.
• I've confirmed the writer published on this beat in the last 30 days.
• Subject line contains the artifact, not the adjective.
• Evidence offer is concrete: "I can share the contract PDF today."
• Provenance is disclosed, including any disinformation risk.
• Exclusive to one writer — no CC, no BCC blast.
• Follow-up scheduled at 72 hours, then seven days, then stop.