LiveActive security incident?Get immediate response
MITRE ATT&CK® Tool

S0683: Peirates

Peirates is a post-exploitation Kubernetes exploitation framework with a focus on gathering service account tokens for lateral movement and privilege escalation. The tool is written in GoLang and publicly available on GitHub.[1]

EnterpriseS0683ToolObject v1.0Modified
Discuss defensive coverageBack to ATT&CK
Glexia's Take · Automated analysis

Security context for executives and security teams

Automation confidenceMedium

S0683: Peirates describes [Peirates](https://attack.mitre.org/software/S0683) is a post-exploitation Kubernetes exploitation framework with a focus on gathering service account tokens for lateral movement and privilege escalation. The tool is written in GoLang and publicly available on GitHub.(Citation: Peirates GitHub)

Executive priority

S0683: Peirates is an official MITRE ATT&CK software. Glexia treats it as defensive behavior context for prioritizing monitoring, control validation, and response planning without using the object by itself as an attribution claim.

Technical view

Security teams should validate S0683: Peirates by reviewing the official ATT&CK relationships, mapped tactics (the mapped ATT&CK tactic context), supported platforms (Containers), and available local telemetry before making detection or mitigation decisions.

Likely telemetry

  • Official ATT&CK relationships and object metadata
  • Cloud control-plane, SaaS audit, and container platform logs

Detection direction

  • Validate whether S0683: Peirates appears in your detection coverage and tabletop scenarios.
  • Use the object to align executive risk language with SOC, incident response, and detection engineering work.
  • Do not treat ATT&CK relationship context as attribution without corroborating evidence.

Mitigation priorities

  • Map the object to existing controls and identify missing telemetry or response ownership.
  • Prioritize mitigations that reduce exposure on the listed platforms and tactics.
  • Review adjacent ATT&CK relationships before changing policy, detections, or reporting language.
Additional notes and limits

Baseline Glexia take generated from the official MITRE ATT&CK STIX object, source hash, tactics, platforms, and detection fields. It is safe to replace with a richer model-generated take for the same source hash later.

This baseline take is source-grounded and schema-validated, but it does not include environment-specific telemetry, incident evidence, or threat-intelligence corroboration.

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Official MITRE ATT&CK definition

Peirates

Peirates is a post-exploitation Kubernetes exploitation framework with a focus on gathering service account tokens for lateral movement and privilege escalation. The tool is written in GoLang and publicly available on GitHub.[1]

View the same entry on attack.mitre.org (MITRE-hosted reference; in-page links above use the Glexia ATT&CK library.)

Glexia analysis

How security teams should use this page

Treat this object as behavior context, not an attribution claim. Validate the related groups, software, data sources, and mitigations against official ATT&CK relationships and your own telemetry before making control-coverage decisions.

ATT&CK relationship table

Techniques used

This mirrors the MITRE pattern of making group, software, campaign, and technique relationships scannable. Relationship notes come from mirrored ATT&CK relationship text when available.

12 rows
DomainIDNameRelationship / procedure
EnterpriseT1613Container and Resource Discovery

Peirates can enumerate Kubernetes pods in a given namespace.[1]

EnterpriseT1609Container Administration Command

Peirates can use `kubectl` or the Kubernetes API to run commands.[1]

EnterpriseT1611Escape to Host

Peirates can gain a reverse shell on a host node by mounting the Kubernetes hostPath.[1]

EnterpriseT1550.001Application Access TokenSub-technique

Peirates can use stolen service account tokens to perform its operations. It also enables adversaries to switch between valid service accounts.[1]

EnterpriseT1530Data from Cloud Storage

Peirates can dump the contents of AWS S3 buckets. It can also retrieve service account tokens from kOps buckets in Google Cloud Storage or S3.[1]

EnterpriseT1046Network Service Discovery

Peirates can initiate a port scan against a given IP address.[1]

EnterpriseT1552.007Container APISub-technique

Peirates can query the Kubernetes API for secrets.[1]

EnterpriseT1619Cloud Storage Object Discovery

Peirates can list AWS S3 buckets.[1]

EnterpriseT1552.005Cloud Instance Metadata APISub-technique

Peirates can query the query AWS and GCP metadata APIs for secrets.[1]

EnterpriseT1528Steal Application Access Token

Peirates gathers Kubernetes service account tokens using a variety of techniques.[1]

EnterpriseT1078.004Cloud AccountsSub-technique

Peirates can use stolen service account tokens to perform its operations.[1]

EnterpriseT1610Deploy Container

Peirates can deploy a pod that mounts its node’s root file system, then execute a command to create a reverse shell on the node.[1]

Associated objects

Groups, software, and campaigns

GroupEnterprise

G0139: TeamTNT

TeamTNT is a threat group that has primarily targeted cloud and containerized environments. The group as been active since at least October 2019 and has mainly focused its efforts on leveraging cloud and container resources to deploy cryptocurrency miners in victim environments.[1][2][3][4][5][6][7][8][9]

Relationship explorer

All related ATT&CK context

uses · GroupG0139: TeamTNTEnterpriseuses · TechniqueT1613: Container and Resource DiscoveryEnterpriseuses · TechniqueT1609: Container Administration CommandEnterpriseuses · TechniqueT1611: Escape to HostEnterpriseuses · TechniqueT1550.001: Application Access TokenEnterpriseuses · TechniqueT1530: Data from Cloud StorageEnterpriseuses · TechniqueT1046: Network Service DiscoveryEnterpriseuses · TechniqueT1552.007: Container APIEnterpriseuses · TechniqueT1619: Cloud Storage Object DiscoveryEnterpriseuses · TechniqueT1552.005: Cloud Instance Metadata APIEnterpriseuses · TechniqueT1528: Steal Application Access TokenEnterpriseuses · TechniqueT1078.004: Cloud AccountsEnterpriseuses · TechniqueT1610: Deploy ContainerEnterprise
Change history

Object version and sync metadata

The fields below describe the current mirrored snapshot. When Glexia retains multiple ATT&CK source imports, you can open the table to compare the same object across releases (hashes and MITRE timestamps). For MITRE’s own release notes and roadmap, see ATT&CK resources — Updates.

ATT&CK release
19.2
Object version
1.0
Created
Modified
Raw hash
6f5edeb9097c83ac...
Imported snapshots across ATT&CK releases(2)
ReleaseBundle importedObject versionModifiedStatusRaw hash
19.21.0Current bundle6f5edeb9097c…
19.11.0Older bundle6f5edeb9097c…
Raw source

Mirrored ATT&CK source object

The raw object is retained through the mirrored ATT&CK source bundle and object hash. The raw endpoint returns the exact object from the mirrored bundle when available.

Open mirrored raw JSONOpen MITRE-hosted copy
Source references

External references and citations

MITRE external references are preserved separately from Glexia analysis so citations remain traceable to their original source records.

  1. [1]
    Peirates GitHub

    InGuardians. (2022, January 5). Peirates GitHub. Retrieved February 8, 2022.

    Open source URL
  2. [2]
    mitre-attackS0683
    Open source URL
Source and licensing

Source: MITRE ATT&CK®. © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. MITRE ATT&CK and ATT&CK are registered trademarks of The MITRE Corporation. Glexia is not affiliated with or endorsed by MITRE.

Official MITRE ATT&CK siteOfficial STIX data repositoryMITRE ATT&CK terms of use