Latest / Tech Talks With Kinsoft / Last Week in Tech – Patch Tuesday's Two Zero-Days, Rockstar's Vendor Breach, and Amazon's $11.6B Satellite Bet

Transcript

Last Week in Tech – Patch Tuesday's Two Zero-Days, Rockstar's Vendor Breach, and Amazon's $11.6B Satellite Bet · Tech Talks With Kinsoft

• 0:00
  Usually, you know, when we talk about diagnosing
• 0:02
  a really complex system, there is this sort of
• 0:04
  comforting expectation of precision. Right, yeah.
• 0:07
  Like you break a bone, you get an x -ray, and
• 0:09
  the doctor just points to that jagged white line
• 0:11
  on the screen. It's broken or it's not broken.
• 0:14
  It's a completely binary, visible reality. It's
• 0:16
  right there in front of you. Exactly. But when
• 0:19
  you look at the digital nervous system of our
• 0:22
  modern world, that x -ray machine is entirely
• 0:25
  useless. The diagnostic landscape we're navigating
• 0:28
  today is just incredibly murky, mostly because
• 0:31
  the real threats, well, they're structural and
• 0:34
  completely invisible. I mean, we really create
• 0:36
  categorization. We want to see the problem clearly.
• 0:40
  But the vulnerabilities in our digital infrastructure,
• 0:43
  they just don't show up on a neat little scan.
• 0:45
  They hide in the spaces between systems, in those
• 0:49
  operational blind spots, and honestly, in the
• 0:51
  sheer massive scale of the networks we've built.
• 0:54
  So welcome to the deep dive. Today, we're looking
• 0:56
  at a really massive update that dropped on April
• 0:59
  20th, 2026 from Kinsoft. Yeah, the Tech Talks
• 1:02
  briefing. Right. Their Tech Talks briefing titled
• 1:04
  Vulnerabilities, Breaches and AI Shifts. And
• 1:08
  our mission today is to basically take what looks
• 1:11
  like a rapid fire tech news roundup. And slow
• 1:15
  it right down. We want to extract the hidden
• 1:17
  patterns for you. Which is so needed right now.
• 1:19
  It really is. We are going to connect the dots
• 1:21
  between microscopic flaws in our code, the structural
• 1:24
  vulnerabilities of corporate supply chains, some
• 1:26
  massive labor restructuring, and the escalating
• 1:30
  battle for global space infrastructure. So, OK,
• 1:34
  let's unpack this. Think of a digital matrix,
• 1:36
  right, just morphing into a global map of data
• 1:39
  streams. Keep that visual in your mind as we
• 1:41
  go through this, because these Kinsoft headlines
• 1:43
  aren't just isolated, you know, IT department
• 1:45
  headaches. Not at all. No, they represent these
• 1:48
  seismic shifts in how modern society operates.
• 1:50
  And really, the most logical place to begin understanding
• 1:53
  this shift is at the absolute microscopic level,
• 1:56
  the literal code that runs the economy. Yeah,
• 1:58
  let's start there, because Microsoft's recent
• 2:00
  patch Tuesday included an absolute avalanche
• 2:03
  of fixes. I mean, 167 in total. That is a staggering
• 2:06
  number. It's wild. And buried in that massive
• 2:10
  pile were two incredibly dangerous zero days.
• 2:13
  I mean, dealing with 167 vulnerabilities is sort
• 2:16
  of like managing security for a massive 100 -story
• 2:19
  skyscraper and suddenly realizing... Oh, 167
• 2:23
  windows were left unlocked. Right. A complete
• 2:25
  logistical nightmare. Exactly. It's a nightmare
• 2:27
  to send teams to secure them all. But a zero
• 2:30
  day that is actively exploited. That means a
• 2:33
  burglar already has the master key and is currently
• 2:35
  inside the building just walking the halls. What's
• 2:39
  fascinating here is how the concept of triage
• 2:41
  becomes so critical. An enterprise environment
• 2:44
  is just, well, it's simply too complex to patch
• 2:47
  simultaneously without breaking essential services.
• 2:49
  You just take the whole system down. Exactly.
• 2:50
  Yeah. Security teams have to prioritize based
• 2:53
  on the potential blast radius. And Kinsoft highlights
• 2:55
  that one of these zero days was an actively exploited
• 2:58
  flaw in SharePoint server, which actually made
• 3:00
  the U .S. government's official must -patch list.
• 3:03
  Yeah, think about the gravity of that for a second.
• 3:05
  A federal government intervening directly in
• 3:07
  corporate software maintenance. SharePoint isn't
• 3:11
  just some basic document viewer. It is the collaborative
• 3:14
  backbone for defense contractors, infrastructure
• 3:17
  operators, massive multinational corporations.
• 3:21
  Right. It's the central nervous system for internal
• 3:23
  strategic data. Precisely. So when the government
• 3:27
  throws up a flare like a must patch mandate for
• 3:29
  SharePoint, it signals a massive systemic risk.
• 3:32
  Hackers aren't just looking to, you know, deface
• 3:35
  public facing websites anymore. Not the good
• 3:37
  stuff. Right. They are embedded in the digital
• 3:39
  filing cabinets where the actual strategic proprietary
• 3:42
  work happens. They're basically establishing
• 3:44
  a beachhead for lateral movement across the entire
• 3:47
  network. And the second zero day kin soft flags
• 3:49
  makes that lateral movement even more terrifying,
• 3:52
  to be honest. It's a publicly disclosed Windows
• 3:54
  Defender privilege escalation bug. Yeah, that
• 3:58
  one is rough. Because Windows Defender is the
• 4:00
  literal security guard of the operating system.
• 4:03
  So privilege escalation basically means a low
• 4:06
  -level intruder, maybe just some basic malware
• 4:09
  that got executed by a careless email click,
• 4:13
  figures out how to manipulate system memory to
• 4:15
  grant itself administrative rights. Right. So
• 4:17
  the malware goes from having guest access in
• 4:20
  the lobby to literally holding the keys to the
• 4:23
  server room. Exactly. It alters its own identity
• 4:25
  within the operating system's hierarchy. I mean,
• 4:28
  the sheer fragility of these systems is just
• 4:30
  staggering when you really look at it. We tend
• 4:33
  to assume enterprise code is solid architecture,
• 4:36
  like poured concrete. Yeah, we want it to be.
• 4:38
  But in reality, it is highly porous and requires
• 4:41
  this frantic, continuous maintenance just to
• 4:45
  keep the roof from caving in on a daily basis.
• 4:47
  But the thing is, and the Kinsoft briefing makes
• 4:49
  this really clear, flawless code doesn't actually
• 4:52
  solve the problem. No, it doesn't. You can lock
• 4:54
  all 167 windows. You can patch your servers,
• 4:57
  secure your endpoints, build a literal fortress.
• 5:00
  It means absolutely nothing if your internal
• 5:03
  architecture automatically unlocks the doors
• 5:04
  for a compromised partner. The supply chain issue.
• 5:07
  Exactly. The briefing details a massive breach
• 5:10
  at Rockstar Games by the Shiny Hunters crew.
• 5:13
  And the wild part is, the attackers didn't brief
• 5:16
  - Rockstar's heavily fortified perimeter directly,
• 5:19
  they slipped in through a third -party vendor.
• 5:22
  Yeah, Rockstar's internal walls held up perfectly
• 5:24
  fine, but their supply chain trembled. Kinsoft
• 5:28
  notes the attackers leaked internal data, though
• 5:31
  they reportedly didn't reach the core game source
• 5:33
  code or the most sensitive player databases.
• 5:36
  Right. But their conclusion is pretty blunt.
• 5:39
  The supply chain is the ultimate soft spot. Okay,
• 5:41
  wait. I need to stop you there for a second.
• 5:43
  Sure. Because if the highly valuable game source
• 5:45
  code is totally safe and the player data wasn't
• 5:48
  even touched, who cares? I mean, isn't this just
• 5:51
  an embarrassing PR headache over some leaked
• 5:53
  Slack messages or internal emails? Why is this
• 5:56
  a major structural warning for the rest of us?
• 5:59
  Well, if we connect this to the bigger picture,
• 6:01
  it matters entirely because of the methodology
• 6:03
  it proves. Modern corporate entities aren't walled
• 6:06
  castles anymore. They're too big for that. Right.
• 6:08
  They're interconnected ecosystems. heavily reliant
• 6:11
  on dozens of external vendors for everything,
• 6:15
  marketing analytics, HR platforms, you name it.
• 6:18
  And to make those vendor relationships functional,
• 6:20
  you have to connect your digital systems via
• 6:23
  APIs and network authentication tokens. Which
• 6:26
  means you are establishing automated, trusted
• 6:28
  pipelines between your secure network and theirs.
• 6:32
  Exactly. You are giving external applications
• 6:34
  permission to read and write data inside your
• 6:37
  fortress. So when Shining Hunters compromised
• 6:39
  that third party vendor, they proved they could
• 6:42
  navigate that trusted pipeline. Wow. It's basically
• 6:45
  like giving your external accounting firm a digital
• 6:47
  key card that is programmed to only open the
• 6:49
  specific financial filing room. But because the
• 6:53
  building's internal API architecture uses these
• 6:55
  interconnected trust protocols, once the attacker
• 6:57
  is inside using the accountant's key card, they
• 7:00
  can often manipulate those permissions to just
• 7:02
  wander into adjacent restricted areas. That is
• 7:04
  genuinely terrifying. Yeah, the fact that he
• 7:07
  didn't hit the source code this time is likely
• 7:09
  just a matter of timing or specific network segmentation,
• 7:12
  not a failure of the attack factor itself. The
• 7:15
  door is propped open. So you are only as secure
• 7:18
  as the absolute weakest vendor you do business
• 7:20
  with. Exactly. Which makes auditing your own
• 7:22
  security posture feel almost impossible. You
• 7:26
  have to somehow audit the security practices
• 7:28
  of every single partner in your supply chain,
• 7:31
  which mathematically just doesn't scale for a
• 7:34
  modern enterprise. And hackers understand this
• 7:36
  math perfectly. They are actively avoiding the
• 7:39
  heavily fortified front doors of the main enterprise
• 7:42
  targets. It is far more efficient to quietly
• 7:45
  slip through the AP. It's the path of least resistance.
• 7:52
  Exactly. It forces a complete paradigm shift
• 7:55
  in cybersecurity. A company is an ecosystem,
• 7:57
  and any introduced pathogen anywhere in that
• 8:00
  ecosystem threatens the entire host. And here's
• 8:03
  where it gets really interesting. That structural
• 8:04
  vulnerability isn't limited to software APIs
• 8:07
  and vendor ecosystems. The human layer itself
• 8:10
  is increasingly viewed as a weakness to be optimized
• 8:12
  out. Yes, the labor shift. Right. The Kinsoft
• 8:16
  briefing highlights Snap announcing a cut of
• 8:18
  around 1 ,000 jobs. And for context, that is
• 8:22
  roughly a sixth of their entire workforce. And
• 8:24
  the explicitly credited reason for this massive
• 8:27
  amputation. AI efficiencies. And the market reaction
• 8:30
  to that was immediate and highly revealing. The
• 8:33
  stock jumped. It did. Kinsoff points out this
• 8:36
  is a very familiar pattern right now across the
• 8:38
  sector. AI is the headline justification for
• 8:41
  both massive capital expenditure and aggressive
• 8:44
  employee layoffs. The paradox here is just staggering
• 8:47
  to me. I mean, executives are actively bleeding
• 8:50
  cash on the balance sheet to acquire or build
• 8:52
  these AI systems. And Wall Street is literally
• 8:54
  cheering them on for shedding human jobs. spending
• 8:58
  billions of dollars to save money. This raises
• 9:00
  an important question about market mechanics.
• 9:03
  To understand the drive here, you have to look
• 9:05
  at how financial markets value human labor versus
• 9:08
  technological infrastructure. Humans are operational
• 9:10
  expenses, OpEx. Right, the day -to -day costs.
• 9:13
  Exactly. They require health care, they experience
• 9:15
  burnout, they need management, and, you know,
• 9:18
  they sleep. From a cold ledger perspective, human
• 9:22
  capital is a heavy recurring liability that scales
• 9:25
  linearly. If you want twice the localized output,
• 9:28
  you generally need to hire twice the humans.
• 9:30
  But AI is treated differently. It's treated as
• 9:33
  a capital expenditure capex. It is an infrastructure
• 9:35
  investment. Scott on. You train the model or
• 9:38
  buy the enterprise license once, and the marginal
• 9:41
  cost of having that algorithm do the work of
• 9:43
  a thousand people approaches zero over time.
• 9:46
  Which Wall Street loves. Oh, they love it. When
• 9:49
  Snap announces they are achieving AI efficiencies,
• 9:51
  they are signaling to the market that they can
• 9:53
  maintain or grow their operational output while
• 9:56
  permanently amputating a massive chunk of their
• 9:58
  recurring liabilities. The algorithm is perceived
• 10:01
  as infinitely scalable, operating 24 -7 without
• 10:04
  benefits or HR disputes. And we aren't just talking
• 10:07
  about abstract efficiencies in a boardroom here.
• 10:09
  We're talking about automating very specific
• 10:12
  workflows, QA testing, first -tier customer support
• 10:15
  triage, basic code generation, the very systems
• 10:18
  we were just talking about patching and securing
• 10:20
  earlier. Exactly, the actual heavy lifting. The
• 10:23
  modern workforce is caught in a brutal pincer
• 10:25
  movement. Rapid capability gains in AI are making
• 10:28
  it genuinely useful for everyday corporate tasks,
• 10:31
  while the financial market actively incentivizes
• 10:34
  companies to prioritize that algorithmic technology
• 10:37
  over human employment. It really is a massive
• 10:40
  economic realignment. I mean, the long term sustainability
• 10:43
  of a consumer economy that systematically reduces
• 10:46
  its human workforce is highly questionable. Who
• 10:50
  buys the products if a sixth of the workforce
• 10:52
  is optimized out? Right. It doesn't make long
• 10:54
  term sense. But the short term market pattern
• 10:56
  is firmly locked in. Algorithmic efficiency equals
• 10:59
  higher future profit margins, which equals higher
• 11:02
  stock prices today. regardless of the localized
• 11:05
  human tool. So to power all these AI efficiencies
• 11:08
  and to maintain these global API -driven vendor
• 11:11
  supply chains we talked about, these tech giants
• 11:14
  need absolute dominance over data transmission.
• 11:17
  They require zero latency and zero disruption.
• 11:20
  Absolutely zero. And to guarantee that, they're
• 11:22
  basically abandoning the terrestrial sphere entirely.
• 11:25
  Which brings us to the final piece of the Kinsoft
• 11:27
  briefing, the board game in the sky. Yeah, they
• 11:30
  are moving the core infrastructure into low Earth
• 11:32
  orbit. It's wild. The update details Amazon making
• 11:35
  a staggering $11 .5 billion bid to acquire the
• 11:39
  satellite operator Global Star. Their goal is
• 11:42
  to bulk up a direct rival to Starlink. It's almost
• 11:45
  like a game of Monopoly. But instead of buying
• 11:49
  Boardwalk and Park Place, we're watching tech
• 11:51
  giants buy up orbital space to control the literal
• 11:54
  pipes of the global Internet. It really is. And
• 11:57
  if you synthesize everything we've analyzed today,
• 11:59
  the microscopic code flaws, the vulnerable supply
• 12:02
  chains, the massive AI infrastructure investments,
• 12:05
  the strategic logic behind an $11 .5 billion
• 12:08
  space acquisition becomes incredibly clear. How
• 12:11
  so? Well, terrestrial infrastructure is just
• 12:13
  an absolute mess of vulnerabilities. Undersea
• 12:15
  fiber optic cables are exposed to everything
• 12:17
  from accidental anchor drags to state -sponsored
• 12:19
  sabotage. Local data centers are subject to regional
• 12:22
  power grid failures. But more importantly, earthbound
• 12:25
  infrastructure is subject to geopolitics. Ah,
• 12:28
  physical borders. Because if you run a fiber
• 12:30
  optic cable through a sovereign country, you
• 12:33
  have to obey that country's laws, their telecommunications
• 12:37
  regulators, and their national firewalls. Exactly.
• 12:41
  Amazon's entire empire, from retail logistics
• 12:44
  to AWS cloud computing to the massive AI infrastructure
• 12:47
  driving their stock price, relies on constant
• 12:50
  unbroken data flow. Right. The ultimate structural
• 12:54
  vulnerability is relying on someone else's physical
• 12:56
  infrastructure, especially when that infrastructure
• 12:59
  is heavily regulated by varying nation states
• 13:01
  with shifting political alliances. Because if
• 13:04
  you don't own the physical pipes, the local government
• 13:06
  can just shut off the water. where they can intercept
• 13:08
  and monitor the flow. Exactly. So by spending
• 13:11
  $11 .5 billion on a satellite network, Amazon
• 13:14
  is bypassing the chaotic, vulnerable, earthbound
• 13:17
  networks entirely. Owning the satellites means
• 13:20
  you own the transmission from space directly
• 13:22
  to the ground hardware entirely on your own terms.
• 13:25
  It effectively bypasses physical terrestrial
• 13:27
  borders. They are basically building a private
• 13:30
  closed loop orbital nervous system. They don't
• 13:33
  have to worry about a compromised local ISP in
• 13:36
  their supply chain or some foreign government
• 13:39
  cutting a cable in a territorial dispute. They
• 13:41
  just beam the data straight down from their own
• 13:44
  hardware in orbit. Precisely. It kind of elevates
• 13:47
  these tech giants into something resembling digital
• 13:49
  nation states. They are no longer beholden to
• 13:52
  the physical geography of the countries they
• 13:54
  actually operate in. And by building a rival
• 13:56
  to Starlink, Amazon is ensuring no single private
• 14:01
  entity holds a monopoly. on that space -based
• 14:05
  sovereignty. This is the modern space race. It
• 14:08
  is not nations competing over geopolitical ideology
• 14:10
  anymore. Wow. It is mega corporations competing
• 14:13
  for absolute data supremacy and infrastructure
• 14:16
  independence. The scale of this transition is
• 14:19
  genuinely dizzying. So what does this all mean
• 14:21
  for you listening at home? Let's quickly recap
• 14:23
  the terrain we've covered today. In just one
• 14:25
  Kinsoft briefing, we've traced a complete spectrum
• 14:28
  of systemic restructuring. We really have. We
• 14:30
  started at the microscopic level, looking at
• 14:33
  how 167 patches and actively exploited zero days
• 14:36
  in SharePoint and Defender highlight the utter
• 14:38
  fragility of the foundational code our economy
• 14:41
  relies on. Then we zoomed out to see how Rockstar's
• 14:44
  API vendor breach proves our interconnected corporate
• 14:47
  ecosystems are incredibly porous. You really
• 14:50
  are only as secure as the external vendor holding
• 14:53
  the digital keycard to your network. And from
• 14:56
  there, we looked at the human layer, analyzing
• 14:58
  the brutal financial logic behind Snap's AI layoffs,
• 15:01
  where companies are bleeding capital to build
• 15:03
  algorithms that simply erase human operational
• 15:05
  expenses. Yeah. And finally, we looked up seeing
• 15:08
  Amazon deploy $11 .5 billion into low Earth orbit
• 15:11
  to bypass terrestrial infrastructure and achieve
• 15:14
  true borderless data sovereignty. The Kinsoft
• 15:17
  update ends with a really simple, vital piece
• 15:19
  of advice. Stay patched. Stay skeptical. It's
• 15:22
  a reminder to examine your own digital footprint.
• 15:25
  your professional supply chains, and your reliance
• 15:27
  on external systems with a highly critical eye.
• 15:30
  Definitely. And as we wrap up this deep dive,
• 15:33
  we want to leave you with a final thought to
• 15:35
  mull over on your own. We've seen how AI efficiencies
• 15:38
  are restructuring the economic value of human
• 15:41
  labor and how megacorporations are deploying
• 15:44
  satellite networks to bypass the physical borders
• 15:46
  and infrastructure of traditional nation states.
• 15:49
  Right, which brings up the ultimate question
• 15:51
  moving forward, one of governance. As these shifts
• 15:54
  accelerate, who actually writes the laws of our
• 15:58
  future digital society? That is the million -dollar
• 16:01
  question. Exactly. If the labor force is managed
• 16:03
  by algorithmic efficiency and the data flows
• 16:06
  through privately owned orbital streams, will
• 16:09
  our lives really be guided by the earthbound
• 16:12
  governments issuing those must -patch lists?
• 16:14
  Or will the true power lie with the private,
• 16:17
  borderless megacorporations that own the AI,
• 16:20
  the supply chains, and the stars themselves?
• 16:23
  It's a lot to think about. We keep looking for
• 16:26
  that clean x -ray, a simple binary picture of
• 16:28
  how our world works and who is actually in charge
• 16:30
  of it. But the deeper we dive into the code and
• 16:33
  the orbital networks, the more we realize those
• 16:35
  old diagnostic tools are completely useless.
• 16:37
  Yeah, they really are. The picture is murky,
• 16:40
  the systems are fragile, and honestly, the only
• 16:42
  way forward is to keep asking the hard questions.
• 16:45
  Thanks for joining us on this deep dive. Stay
• 16:47
  curious, stay skeptical, and we'll see you next
• 16:49
  time.