/
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
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

Microsoft confirms Lapsus$ compromised “a single account” and stole portions of source code for some products, but says no customer code and data was involved

Lapsus$ says it has accessed data from Okta, Nvidia, Samsung, and Ubisoft  —  The hacking group Lapsus$ …

The Verge

Context & Ripple Effects

Microsoft’s confirmation narrows the scope of the previously alleged 37GB source-code release: one account was compromised, with no customer code or data involved. It also places Microsoft alongside Nvidia, where Lapsus$-linked attackers had already exposed employee and proprietary information, and Okta, where an engineer’s laptop was accessed.

Related coverage describes Lapsus$ as an extortion group that targets large companies by bribing or tricking employees, making the single-account detail consequential: the group’s reported access route centers on workforce identity controls rather than a broad product-system breach.

First-order effects

  • Microsoft must assess and remediate the affected product source code while communicating a bounded incident scope to customers: portions of code were taken, but customer code and data were not involved.
  • Okta faces sharper scrutiny from customers after its confirmation of access to an engineer’s laptop, as Microsoft’s account compromise reinforces the operational stakes of identity-system exposure.

Second-order effects

  • Nvidia, Okta, Samsung, and Ubisoft face intensified pressure to clarify their own exposure because Lapsus$ has claimed access across all five companies, and Microsoft has now confirmed part of the group’s claims.
  • Source-code theft becomes a dual risk for software vendors: leaked code can aid attackers’ understanding of products while forcing affected companies to devote engineering effort to review and remediation.

Third-order effects

  • If employee-focused intrusion methods continue to yield proprietary code at major vendors, security investment will shift further toward protecting privileged accounts and employee-facing support processes, not just perimeter systems.
  • The episode points to an extortion model in which compromises of a small number of employee accounts can create industry-wide trust consequences across software suppliers and their customers.

The trend: Lapsus$ is a data-extortion campaign illustrating how employee-account compromise can turn internal code and identity access into leverage against major technology vendors.

Discussion

  • @msftsecurity @msftsecurity on x
    Microsoft Security has been tracking criminal actor DEV-0537 (LAPSUS$) targeting organizations with data exfiltration and destructive attacks - including Microsoft. Analysis and guidance in our latest blog: https://www.microsoft.com/...
  • @shoghicp @shoghicp on x
    SCP-0537? “DEV-0537 is known to monitor and intrude in incident response communications. As such, these communication channels should be closely monitored for unauthorized attendees and verification of attendees should be performed visually or audibly.” https://www.microsoft.com/…
  • @raj_samani Raj Samani on x
    LAPSUS$ “has been observed joining the organization's crisis communication calls and internal discussion boards (Slack, Teams, conference calls, and others) to understand the incident response workflow” https://www.microsoft.com/... #cybersecurity #infosec #malware H/T @msftsecur…
  • @aiddya Ashanka Iddya on x
    This blogpost genuinely made my jaw drop. Very good guidance here for organizations from @MsftSecIntel https://twitter.com/...
  • @krisnova @krisnova on x
    Fascinating to watch Microsoft respond to LAPSUS$ (responsible for the Okta breach) who clearly isn't playing by the rules here. “Unlike most activity groups that stay under the radar [LAPSUS$] doesn't seem to cover its tracks” https://twitter.com/...
  • @runasand Runa Sandvik on x
    Next time you need to explain why JIRA, GitHub, or Slack are not great ways to store and/or share credentials, show this Microsoft post about Lapsus$. https://www.microsoft.com/... https://twitter.com/...
  • @billdemirkapi Bill Demirkapi on x
    Microsoft published a great technical dive into the methodology of LAPSUS$. Worth a read if you're an organization trying to assess your own risk or want to learn more about how they operate. https://www.microsoft.com/...
  • @nixcraft @nixcraft on x
    This is so wild. DEV-0537 (LAPSUS$) Criminal actor targeting organizations https://www.microsoft.com/... This group is publicly offering money to employees for credentials, VPN and other data. I never heard any hacking group doing such thing previously. Stay safe everyone.