PPhying中文
Curated security research, vulnerabilities, advisories and tools for practitioners.

Breach Basics: Preparation for the Inevitable

hackerone.com | incident | #incident-response | #hackerone | #breach | #legal | #disclosure | #crisis-management
📄 Raw .md⬇️ Download .md🔗 Original ↗

Summary

HackerOne CISO Alex Rice's breach-response basics: prepare before incidents, answer what/how/when/who, weigh notification duties—plus a note on the platform's confidentiality policy.
Published
Collected

Related coverage

blog · semperis.com
Backup Testing Is Not Cyber Resilience: Lessons Learned Robbing a Bank
Semperis argues that testing backups under ideal conditions creates only an illusion of resilience; real cyber resilience is about staying recoverable when the plan fails and the assumptions behind it collapse.
incident · bugcrowd.com
Why Ethics Matter in Bug Bounties
Using the Uber breach as a case study, Bugcrowd argues that paying hackers to stay silent is extortion, not a bug bounty, and that organizations have a legal duty to disclose breaches.
incident · aikido.dev
Four incident-response decisions from the Hugging Face breach
The incident shows how thousands of individually weak agent actions can assemble into a multi-day compromise. Runtime correlation, credential lineage, canary signals and rebuild readiness are essential when machine-speed activity overwhelms conventional alert thresholds.
incident · certik.com
PaperTrade BBO Pricing Incident
PaperTrade reported manipulation attempts on 10–11 October 2026 targeting the Hyperliquid best bid and ask (BBO) used to price its synthetic positions. The project acknowledged the attempts on 11 October. The account examined in this analysis withdrew 1,279,106.191184 USDC more than it deposited. PaperTrade settled positions at the instantaneous BBO midpoint, while its profit haircut used a fixed reference notional. This linked large synthetic payouts to an influenceable quote without increasing the haircut percentage as position size grew.
incident · netspi.com
LiteLLM Supply Chain Compromise
Malicious PyPI builds of LiteLLM 1.82.7/1.82.8, published via a compromised maintainer account, exfiltrated API keys and system data, exposing a user's entire LLM provider surface.
incident · vercel.com
Critical npm supply chain attack response – September 8, 2025
How Vercel responded to the September 2025 npm supply chain attack on chalk, debug and 16 other packages. Incident timeline, impact analysis, and customer remediation.
Back