Protocol - Login overload

We do not have enough information to reproduce this issue.

Please include the following information to help us understand your problem:

Steps to Reproduce:
1. (Explain what needs to be done for the issue to happen)
2.
3.

Observed Results:
(Briefly describe what happens)

Expected Results:
(Briefly describe what should happen)

Please also attach any needed commands, datapacks, resourcepacks, screenshots, videos, or worlds needed to help reproduce this issue.

Refer to the Bug Tracker Guidelines for more information about how to write helpful bug reports. Bug reports with insufficient information may be closed as Incomplete.

_{This issue is being temporarily resolved as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.}

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 BDS Wiki – 📖 FAQs

Steps to Reproduce:

1. Use a bot library, such as bedrock-protocol or gophertunnel. For this example, we will use bedrock-protocol.
2.  Install the library and modify the login process. Specifically, change line 80 in the file `keyExchange.js` (located at https://github.com/PrismarineJS/bedrock-protocol/blob/master/src%2Fhandshake%2FkeyExchange.js) to something like "setInterval(() => client.write('client_to_server_handshake', {}), 0)" and then save the file. 
3. Use an example script to connect to the server.

Observed Results:

The client connects to the server, and the console logs that the client has connected multiple times.

Expected Results:

Only a single log entry indicating that the client has connected should be generated and the client should be disconnected for something like bad packet/unexpected packet after sending more than one client to server handshake packet.

MEQS_KEEP_PRIVATE

Thank you for your report!
However, this issue is Invalid.

The server you are playing on is modified.
If you can reproduce the issue in a vanilla environment, please recreate the issue.

• Any non-standard client/server build needs to be taken up with the appropriate team, not Mojang.
• Any plugin issues need to be addressed to the creator of the plugin, add-on or resource pack.
• If you have problems on large servers, such as Lifeboat, please contact them first as they run modified server software.

Quick Links:
📓 Bug Tracker Guidelines – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 BDS Wiki – 📖 FAQs

The server is not modified in a single way it is a normal windows BDS the issue is that malicious threat actors will use these bugs in BDS to spam servers

 Plugins do not have any relation to this issue as it's a issue with the protocol