/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Symantec says it wasn't impacted by Fxmsp hack, denies being contacted by researchers, who refute Symantec's claim; Trend Micro calls hack a “low risk” incident

Symantec, Trend Micro, and McAfee—b/c their names had been offered up on reddit, twitter & in one article this morning as maybe victims. Trend Micro confirmed it's working w/ law enforcement. Symantec denied being notified & assumes it's clear. Jeremiah Grossman / @jeremiahg : If recent source code of major AV vendors begins circulating publicly, we should expect to see a notable uptick in the number of CVEs. https://twitter.com/... Dell Cameron / @dellcam : So it appears Symantec, Trend Micro, and (likely) McAfee are the three companies. (McAfee sent me a “we're investigating” reply, but did not answer when asked specifically if AdvIntel had reached out.) The first two I can confirm are companies Fxmsp claims it breached. Dell Cameron / @dellcam : AdvIntel also took issue with Trend Micro's claim that no source code was accessed, saying “This statement is incorrect based on the portion of the data we have and the actor's statement.”

Gizmodo Dell Cameron