Skip to main content
Back
IntrusionKubernetes
7 min read

Slow Pisces Kubernetes intrusion at a cryptocurrency exchange

Victim
An unnamed cryptocurrency exchange
When
Mid-2025; Unit 42 gives no month or dayDisclosed Apr 6, 2026
Entry
Spearphishing of a developer gave persistence on a workstation, and the attacker used the developer's privileged cloud session to deploy a malicious pod in the production Kubernetes cluster.

In mid-2025, per Unit 42, an attacker spearphished a developer, used the developer's privileged cloud session to deploy a malicious pod in an exchange's production Kubernetes cluster and took the mounted token of a highly privileged management service account. With it the attacker enumerated secrets, worked with workloads across namespaces, backdoored a production pod, moved into the cloud platform and reached the financial infrastructure, and millions of dollars in cryptocurrency were stolen. Unit 42 names no exchange, cloud provider or month, ties the case to the Slow Pisces campaign by its own statement, gives no timestamps (the step order follows its prose) and describes no containment.

What happened

Internet
+ spearphishing foothold
+ privileged cloud session
+ cluster access
Developer Workstation
Production Kubernetes Cluster
+ cloud-hosted backend
+ sensitive credentials
+ wider cloud platform
Cloud Platform
+ exchange financial infrastructure
+ exit route not described
+ cryptocurrency funds
Financial Infrastructure
Malicious Pod
Management Token
Kubernetes API Server
Cluster Secrets
Production Pod

Replaying the Slow Pisces mid-2025 intrusion

  1. 1

    Workstation foothold

    Mid-2025

    Spearphishing gives the attacker persistence on a developer's workstation; the report gives no month, day or lure.

  2. 2

    Privileged session, malicious pod

    Mid-2025

    The attacker uses the developer's active, privileged cloud session to deploy a malicious pod that exposes the mounted token of a management service account.

  3. 3

    Cluster control

    Mid-2025

    The token authenticates to the Kubernetes API server; the attacker enumerates secrets, works with workloads across namespaces and places a backdoor in a production pod.

  4. 4

    Pivot to the cloud

    Mid-2025

    The token's privileges reach the wider cloud platform, where the attacker retrieves sensitive credentials; the report does not say how the privileges reach it or which provider hosts it.

  5. 5

    Funds taken

    Mid-2025

    The attacker reaches the exchange's financial infrastructure, and millions of dollars in cryptocurrency are stolen, with no exact figure given.

Impact

Millions of dollars in cryptocurrency stolen, per Unit 42, with no exact figure; one malicious pod deployed and one production pod backdoored, secrets enumerated, workloads reached across namespaces, and the exchange's cloud-hosted backend systems and financial infrastructure reached.

Outcome

Where Kubernetes and cloud controls fit

A phished workstation held a privileged cloud session, and one pod exposed the token of a management service account with broad RBAC permissions. An admission policy in your cluster could have narrowed who may deploy a pod there, and bound service-account tokens could have bounded a copy of the token. Permission boundaries, IAM deny policies and account segmentation could have kept the token's reach away from the cloud backend and the financial infrastructure. The workstation and the exchange's own financial systems stay outside every cloud control. If a CI/CD service account in your cluster has broad RBAC, ask what its token would reach.

Could this have been prevented?

In hindsight, no control would have stopped it. 3 controls would have limited how far it went. 8 steps have no cloud-provider control. The counts below are control assessments, not attack stages: several can address the same step. The same replay with the controls in place before the incident shows where each phase would have been refused or bounded.

0
Prevented
3
Contained
8
Not covered

How it could have been prevented

The same replay with the controls in place. Green marks where a step is refused, blue where it is bounded, and red where no control reaches it. Open a row to read the control, why it acts, and its caveat.

Internet
+ spearphishing foothold
+ privileged cloud session
+ cluster access
Developer Workstation
Production Kubernetes Cluster
+ cloud-hosted backend
+ sensitive credentials
+ wider cloud platform
Cloud Platform
+ exchange financial infrastructure
+ exit route not described
+ cryptocurrency funds
Financial Infrastructure
Malicious Pod
Management Token
Kubernetes API Server
Cluster Secrets
Production Pod

Replaying the Slow Pisces mid-2025 intrusion

1 · Workstation foothold

1 Not covered

2 · Privileged session, malicious pod

2 Contained1 Not covered4 on other clouds

3 · Cluster control

1 Contained5 Not covered

4 · Pivot to the cloud

4 on other clouds

5 · Funds taken

1 Not covered4 on other clouds

Key facts

  • Unit 42 dated the intrusion only as mid-2025 and published the case on April 6, 2026; the report names neither the exchange nor its cloud provider
  • Spearphishing gave the attacker persistence on a developer's workstation, and the attacker used the developer's active, privileged cloud session to deploy one malicious pod in the production cluster
  • The pod was built to expose the mounted token of a highly privileged management service account with broad RBAC permissions, used by a common CI/CD automation and cluster orchestration system; the report does not say how the pod came to hold that account's token
  • With the token the attacker authenticated to the Kubernetes API server, enumerated secrets, worked across namespaces and placed a backdoor in one production pod; the report gives no count of secrets or namespaces
  • The attacker then moved into the wider cloud platform, retrieved sensitive credentials and reached the exchange's financial infrastructure; millions of dollars in cryptocurrency were stolen, with no exact figure and no description of how the funds left
  • Unit 42 connects the intrusion to a Slow Pisces campaign on its own statement, shows no evidence for it on the page, and describes no containment or fix by the exchange

Sources

Every fact in this breakdown comes from the public reporting below. The replay is a model of that reporting, not a reconstruction of the environment it describes.

  1. 1.
    Understanding current threats to Kubernetes environmentsPalo Alto Networks Unit 42 · Apr 6, 2026 · ResearchCase 1: the attack chain, the service-account token, the cluster privileges, the cloud pivot, the Slow Pisces attribution, the recommended defenses
  2. 2.
    Kubernetes attack surface explodes, number of threats quadruplesTechzine · Apr 20, 2026 · NewsAttribution context: the group's other names and its earlier incidents, as reported from Unit 42

The estate in the replay is illustrative and drawn at the level of attack stages; the victim's real environment is not public. Verdicts describe what a control does when it is in place before the incident. They are not an assessment of the victim's security program.

More cloud attack breakdowns

All breakdowns