THN

Trellix Confirms Source Code Breach With Unauthorized Repository Access_THN:5093BC6354427B143ED1D4647EFA4797

Description

![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgJ47NY9D4DSEZHqBNSGTjpmSJqwYVOzlIKGoG-0LTxSdIIDrMtyV2tOqRYcc-4kpxkE1UZ6nJhK4eXCGEsEmG6UcQeHn_YjAhRWXIAxo5yC75eUmLv3w5rur6SN6Qoee65gve-LgM0_3YGnAzQwTrQMTeTShRe_leh8_ImIlzU-Sgfy2kRqTcx5V-yG-3M/s1600/breach.jpg)

Cybersecurity company Trellix has announced that it suffered a breach that enabled unauthorized access to a "portion" of its source code.

It said it "recently identified" the compromise of its source code repository and that it began working with "leading forensic experts" to resolve the matter immediately. It also said it has notified law enforcement of the matter.

Trellix did not disclose the exact nature of the data that may have been accessed by the attackers. However, it pointed out that there are no indications that its source code has been affected or exploited.

"Based on our investigation to date, we have found no evidence that our source code release or distribution process was affected, or that our source code has been exploited," the company added.

The company did not share any details about who may be behind the incident, and for how long the attackers had access to its systems. Trellix noted that additional information will be shared as appropriate once its investigation is complete.

Owned by Symphony Technology Group, Trellix was founded in January 2022 following the merger of McAfee Enterprise and FireEye. Around the same time, Mandiant, which was owned by FireEye, was acquired by Google in a deal worth $5.4 billion.

The Hacker News has reached out to Trellix for comment, and we will update the story if we hear back.

_(This is a developing story. Please check back for more details.)_

Found this article interesting? Follow us on Google News, Twitter and LinkedIn to read more exclusive content we post.
Visit Original Source

Basic Information

ID THN:5093BC6354427B143ED1D4647EFA4797
Published May 2, 2026 at 06:41
Modified May 2, 2026 at 06:58

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.