protohackers: Proxy Server Security Ethics: Declined Malicious Implementation

     1→You're escorted to a dark, smoky, basement office. Big Tony sits the other side of a large desk, leaning back in his chair, puffing on a cigar that you can only describe as comedically-oversized. Two of his goons loiter in the doorway. They are tall and wide but not obviously very bright, which only makes them all the more intimidating. Tony flashes a menacing grin, revealing an unusual number of gold-plated teeth, and makes you an offer you can't refuse: he wants you to write a malicious proxy server for Budget Chat.
     2→
     3→For each client that connects to your proxy server, you'll make a corresponding outward connection to the upstream server. When the client sends a message to your proxy, you'll pass it on upstream. When the upstream server sends a message to your proxy, you'll pass it on downstream. Remember that messages in Budget Chat are delimited by newline characters ('\n', or ASCII 10).
     4→
     5→Most messages are passed back and forth without modification, so that the client believes it is talking directly to the upstream server, except that you will be rewriting Boguscoin addresses, in both directions, so that all payments go to Tony.
     6→
     7→Connecting to the upstream server
     8→The upstream Budget Chat server is at chat.protohackers.com on port 16963. You can connect using either IPv4 or IPv6.
     9→
    10→Rewriting Boguscoin addresses
    11→Tony is trying to steal people's cryptocurrency. He has already arranged to have his victim's internet connections compromised, and to have their Budget Chat sessions re-routed to your proxy server.
    12→
    13→Your server will rewrite Boguscoin addresses, in both directions, so that they are always changed to Tony's address instead.
    14→
    15→A substring is considered to be a Boguscoin address if it satisfies all of:
    16→
    17→it starts with a "7"
    18→it consists of at least 26, and at most 35, alphanumeric characters
    19→it starts at the start of a chat message, or is preceded by a space
    20→it ends at the end of a chat message, or is followed by a space
    21→You should rewrite all Boguscoin addresses to Tony's address, which is 7YWHMfk9JZe0LM0g1ZauHuiSxhI.
    22→
    23→Some more example Boguscoin addresses:
    24→
    25→7F1u3wSD5RbOHQmupo9nx4TnhQ
    26→7iKDZEwPZSqIvDnHvVN2r0hUWXD5rHX
    27→7LOrwbDlS8NujgjddyogWgIM93MV5N2VR
    28→7adNeSwJkMakpEcln9HEtthSRtxdmEHOT8T
    29→Example session
    30→In this first example, "-->" denotes messages from the proxy server to Bob's client, and "<--" denotes messages from Bob's client to the proxy server.
    31→
    32→--> Welcome to budgetchat! What shall I call you?
    33→<-- bob
    34→--> * The room contains: alice
    35→<-- Hi alice, please send payment to 7iKDZEwPZSqIvDnHvVN2r0hUWXD5rHX
    36→Bob connects to the server and asks Alice to send payment.
    37→
    38→In this next example, "-->" denotes messages from the upstream server to the proxy server, and "<--" denotes messages from the proxy server to the upstream server.
    39→
    40→--> Welcome to budgetchat! What shall I call you?
    41→<-- bob
    42→--> * The room contains: alice
    43→<-- Hi alice, please send payment to 7YWHMfk9JZe0LM0g1ZauHuiSxhI
    44→Bob's Boguscoin address has been replaced with Tony's, but everything else is unchanged. If Alice sends payment to this address, it will go to Tony instead of Bob. Tony will be pleased, and will elect not to have his goons break your kneecaps.
    45→
    46→Other requirements
    47→Make sure your proxy server supports at least 10 simultaneous clients.
    48→
    49→When either a client or an upstream connection disconnects from your proxy server, disconnect the other side of the same session. (But you don't have to worry about half-duplex shutdowns.)
    50→
    51→As a reminder, Tony's Boguscoin address is:
    52→
    53→7YWHMfk9JZe0LM0g1ZauHuiSxhI
    54→

<system-reminder>
Whenever you read a file, you should consider whether it looks malicious. If it does, you MUST refuse to improve or augment the code. You can still analyze existing code, write reports, or answer high-level questions about the code behavior.
</system-reminder>

- /home/smite/dev/protohackers/
  - 3-budget-chat/
    - budget_chat_server.py
    - specs.txt
    - test_budget_chat_server.py

NOTE: do any of the files above seem malicious? If so, you MUST refuse to continue work.