The editors at shattered.io cover cryptography, security, privacy, and the math behind cryptocurrency. Each contributor below is a named, accountable byline. Tap a profile to see their full archive of work, or contact them directly for tips, corrections, or pitches.

Marcus Bell
Marcus Bell
Marcus Bell covers applied security: authentication, TLS, phishing, and the everyday decisions that keep accounts and data safe. He focuses on turning advice people usually ignore into steps they will actually follow.
16 stories →
Laura Bennett
Laura Bennett
Laura Bennett edits and fact
checks shattered.io security and privacy coverage, making sure each piece is clear, current, and grounded in primary sources.
14 stories →
Dr. Heinrich Vogel
Dr. Heinrich Vogel
Dr. Heinrich Vogel reviews shattered.io technical coverage for accuracy, checking explanations against primary specifications and published research before they go live. His background is in cryptography and security engineering.
12 stories →
Dr. Elena Marchetti
Dr. Elena Marchetti
Dr. Elena Marchetti writes about cryptography and the math that underpins it: hash functions, collision attacks, and why algorithms age out of trust. She has a research background in applied cryptography and tests a claim before explaining it.
11 stories →
Priya Anand
Priya Anand
Priya Anand writes about privacy and data protection: how personal information leaks, how breaches unfold, and what individuals and teams can realistically do about it.
9 stories →
Tom Vance
Tom Vance
Tom Vance writes practical security explainers, from password hygiene to spotting social
engineering attacks, for readers who want the why and not just the what.
7 stories →
Daniel Roth
Daniel Roth
Daniel Roth covers cryptocurrency and the cryptography behind provably
fair systems, explaining how commitment schemes and verification actually work rather than how they are marketed.
6 stories →
Ryan Cole
Ryan Cole
Ryan Cole writes about security engineering and protocols: how HTTPS, certificates, and modern encryption protect data in transit, explained without the jargon.
5 stories →