Hacker says to release full Norton Antivirus code on Tuesday
(Reuters) - A hacker who goes by the name of ‘Yama Tough’ threatened Saturday to release next week the full source code for Symantec Corp's flagship Norton Antivirus software. “This coming Tuesday behold the full Norton Antivirus 1,7Gb src …
Context & Ripple Effects
Reuters reports that a hacker using the handle 'Yama Tough' announced on Saturday a plan to publish what he claims is the full 1.7GB source tree for Norton Antivirus on Tuesday, putting Symantec's flagship consumer security product at the center of a disclosure the company did not choose.
The threat lands on a brand already carrying a trust scar: in May 2007 a faulty Norton AntiVirus virus-database update crashed millions of PCs, so any question about the integrity of the product's code touches a customer base that has been burned before.
First-order effects
- Symantec heads into Tuesday needing to verify whether the claimed 1.7GB dump is authentic Norton Antivirus code and decide how to brief enterprise and consumer customers before the files circulate.
- Yama Tough converts a private possession into a timed public event, using the announcement window itself to maximize pressure and attention on Symantec.
Second-order effects
- Competing antivirus vendors gain a sales opening to question code-exposure risk, while Symantec's enterprise buyers must judge whether published source meaningfully changes the attack surface on machines running Norton products.
- Security teams that standardize on Symantec face fresh vendor-risk reviews, since a confirmed leak would let attackers study the flagship product's internals directly.
Third-order effects
- If the release goes ahead, it reinforces a pattern in which stolen corporate source code is used as public leverage rather than sold quietly, pushing software vendors to operate as if their code will eventually be public.
- For security vendors specifically, whose product is trust, repeated source exposures would accelerate a shift toward architectures and response plans built on the assumption of code compromise.
The trend: Hackers are moving from hoarding or quietly selling stolen source code to publishing it on a schedule as leverage against major software vendors.