NGChuen
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # Title Traffic analysis of online game "Pixel Starships" and MITM attack against it # Abstract Online game players' virtual possessions should be secured by game developers, otherwise the attackers could benefit from attackers and cause great loss to game players. In the paper, we investigate Pixel Starships, an online game which doesn't protect the market buying. We demonstrate that we could successfully launch a man-in-the-middle attack, causing virtual possessions loss to the player. # Introduction With the rapid development of the game industry in the past two decades, online games enjoys an important market share, with many people playing them in daily life. Online game developers can profit from their games in various ways. One typical bussiness model is that a player could pay some money for some "virtual possessions". For example, developers could sell powerful weapons to players who want to have better chance of winning in a battle with other players. Usually, players' virtual possessions are important for their game experience. Players may spend large amount of money to buy virtual possessions. Therefore, it is very important that their virtual possessions are protected and secured by the game developers, preventing their possessions from being "stolen" or "corrupted" by potential attackers. Attackers have such intention because many times they can benefit from such attack. In Metaverse \cite{ref2}, players may own real estate and it's important the ownership is protected. Pixel Starships is a bad example of virtual possessions security. The network traffic between player and the game server is unencrypted, allowing man-in-the-middle attackers to modify the traffic. In this paper, we analyze its network traffic and successfully launch an MITM attack against a player. The player suffers loss of 6 "starbuck", while the attacker gain it. ![](https://i.imgur.com/uVqQcNU.jpg) # Related Work MITM remains an important attack method in the real world. In 2017, credit score company Equifax removed its apps from Google and Apple after a breach resulted in the leak of personal data. A researcher found that the app did not consistently use HTTPS, allowing attackers to intercept data as users accessed their accounts.[^MITM] # Methodology ## Threat Model In this paper, we focus on against the missing immutability of the game traffic. Similar to the classic MITM attack, we assume the attacker can monitor and modify the traffic between game client and game server. In practice, the players play games by connecting to a wireless network. If the player is connected to some untrusted public WiFi, the MITM attack becomes possible. Since Pixel Starship can be played on mobile phone, it is realistic. ## Attack Workflow As illustrated in Fig.1, our attack starts from posting a useless item with high price to the market. Then we will guide the victim to buy this useless item with high price by two key steps below. 1. Modify market list. To guide the victim buy our uselesss item, we must let the victim think it is a good deal. If the victim is requesting a market list from the game server, our MITM server will hijack the traffic and modify the price of attacker's item to a very low price. 2. Modify purchase packer. After the victim clicked the purchase button on the attacker's item, the MITM server will modify the purchase packet to restore some field that has been modified in previous data exchange so that the game server will not realize there is a MITM. Once all the attack steps are completed, the victim loses a lot of money that the attacker can gain. ![Figure 1: Attack Workflow](https://i.imgur.com/u1RmYGl.png) # Evaluation Before we could launch an attack, we use wireshark to analyze the network traffic between the game client and server. We use "http contains pixel" to filter out traffic unrelated to the game. Since the game uses HTTP protocol, we could easily obtain the content of each request and response, and guess their semantics according to parameter key and value name. After looking at several packets captured by wireshark, we get to understand two key APIs used in the PSS market. One API is for listing available items on the market. This is an HTTP get request. An example request is shown as follow: ``` params = { 'itemSubType': None, 'rarity': None, 'currencyType': 'Unknown', 'itemDesignId': 0, 'userId': 0, 'accessToken': '4a7bea4b-88bb-4fdd-8fc2-0754e1ee9ba4', } ``` The access token is established when the PSS game is started. Another API is for purchasing an item. This is an HTTP post request. An example request is shown as follow: ``` params = { 'saleId': 24606089, 'clientDateTime': '2022-05-08T19:01:07', 'checksum': '5b96d54b0b54dae4e0b084d444786a11', 'accessToken': '3f4f7cb3-38d9-4204-b9d3-8cc16aaa39e4', 'allowConversion': True, } ``` The saleId indicates which item (posted by a seller) the buyer wants to buy. After we understand the protocols, we try to launch an MITM attack. The attack environment is in one Windows 11 Education Build 22621.1 machine, with pixel starships installed through Steam. We create two Pixel Starships account, one for the victim and one for the attacker. We first modify the host file, letting the attacker's server become the man in the middle. Then the attacker posts to the market an item priced 6 starbucks. Then the victim enters the market, sending an HTTP request to get the list of available items. The attacker's MITM server forwards this request to the game server. When the item list returns, the MITM server modifies attacker's item's price to 1 gas (which is cheap). When the victim sees attacker's item priced 1 gas which is rendered in the game client, he decides to buy it. The victim observes that the total amount of gas he owns decreases by 1. When the victim's game client resynchronizes with the server, he will surprisingly find that he has lost 6 starbucks, instead of 1 gas. From the attacker's perspective, the attacker gets 6 starbucks. # Future Work In this work, we lauch an MITM attack to "steal" starbucks from a victim. However, this kind of attack badly restricts the attackers' ability, requiring the victim to stay online when the attack happens. As a reason, we leave off-path attack as our future work. In the future, we could reverse engineer the Pixel Starships client in order to know how the access token and checksum is generated. If we have such knowledge, we could launch an off-path attack even when the victim is offline. Attack of such kind could do more harm, since it could target a larger number of victims. # References # Proposol here: # Proposal ## Content - Problems to work on and the importance of our work - The focus of our research will be on the market on Pixel Starships. We are going to, first, analyze the network traffic of the market and understand the protocol used by it. Second, based on the understood and vulnerable protocol, a meticulously designed Man-In-The-Middle attack method against the Pixel Starships market buyer (rather than the server) will be proposed by us. Finally, we are going to propose some effective defence that mitigates such dangerous MITM attack. - The reason for which we choose the market as our subject is because it uses HTTP protocol and unencrypted traffic, which is vulnerable. Such practice could open up a great variety of opportunities, including MITM attack, for the attackers. - The importance of this project lies in two aspects. First, Pixel Starships market is a perfect demonstration of what consequences using unencrypted protocol could lead to. Second, our proposed MITM attack will become a good example of how to exploit such vulnerable protocol. - Here follows a more detailed description of what Pixel Spaceships market does. There are two main sorts of actors in the market, namely, buyers and sellers. All actions in the market should go through the game server. The sellers can post an item to the market by sending a request to the server; The (potential) buyers can ask server what are the available items on the market; The buyers can also buy an item by sending another request. - Our proposed MITM attack will sit on the network channel between buyers and the market server. The attacker can modify the network traffic between them. As a consequence, the buyers (victims) could suffer money losses from such MITM attack. - Related work - Tentative approach - Firstly, we plan to poison local DNS, for example, by modifying the DNS record of api2.pixelstarships.com to the address of our MITM server. Then we implement the MITM server. In general, the MITM server just forwards traffic between victim and game server. If MITM detects that the traffic from the victim is about the market, the MITM server will modify some key fields in the traffic and forward it to the game server, directing the victim to purchase the attacker's item. - If the victim really purchased the attacker's item without clicking the corresponding botton, we succeeded. - Evaluation - We used wireshark to capture the traffic of Pixel Starships. We found the game client communicate with server over HTTP protocol and the traffic is unencrypted. Therefore we believe the MITM attack is possible. ![](https://i.imgur.com/ah3wgwz.png) [^MITM]: 2022. Man in the Middle (MITM) Attack. https://www.veracode.com/security/man-middle-attack [^META]: Metaverse. https://en.wikipedia.org/wiki/Metaverse [^PSS]: 2022. Pixel Starships. https://www.pixelstarships.com/

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully