Tag: Gemini

Even if you added so many protections to your game. But adding a honeypot is key to deer malicious automated processes/bots/scripts from attacking your digital masterpiece. However; many developers may be caught off-guard when they come back to their projects,and discovered parts of their work has been pruned without warning. Assumptions by bad actors, and developers who assumed refactoring makes the code run faster can break your game altogether. However; adding measures that are essential ensures your masterpiece is protected altogether.

Protections Notices is very important, but agents.md file in one place is not enough

Earlier; I’ve experimented on added protection notices to my game as I added so many agents.md files across the entire code base as a way to ensure this game is protected against malicious actors/automated processes that can prune your work without warning.

As I prompted Gemini via Google AI Studio; I always ask to pause, and ask for verification. What I didn’t know… it suggested me to add protections notices markdown file to prevent unsolicited refactoring, stubbing, and pruning of my code base. Also, I implemented more protections across the entire code base, and ensure each code is documented and ensure my code base is preserved and properly linked to prevent errors from happening.

Think about a security officer who protects your establishment against terrorism of any kind!

Why Creating A Honeypot Is Very Important?

This is a very important piece of computer science what we need to consider when making a game via AI Studio. This key security measure traps automated processes that are malicious. For this instance; you have a game that focuses on riding donkeys, and a church where you attend protects their work against tampering/modifications that are not authorized. They implement a honeypot that is an intentional typo of a game title, truncated version of a game, or even a set of zip files with multiples of matrices that are designed to halt these malicious automated bots and other unwanted scripts/processes.

How Did I Accomplished This?

I asked Gemini the following:

• Create honeypot folders that are outside of an “src/” folder – This is a first step of building a honeypot.
• Given a honeypot a name that is obvious – I make it obvious as a way to trick malicious processes, scripts, crawlers, and other bad bots. This is key to make it extremely difficult to reach my source code.

• Create special zip files and a lightweight dedicated src folder inside the main honeypot folder – This obvious technique is very important because of the following:

  • Serves as a trap to fool these malicious bots.
  • Makes it extremely difficult for these bots to reach a regular “src/” folder of your app/game.
  • Optionally, you can include lightweight games that are retro, and give them unusual title names, and mechanics.

I did these experiments from a beta version of my game, and spread it to my stable copies of my games what I’ve established.

I’ve also made multiple variants of honeypots for my games as a way to make this security system resilient as possible. Think about improving security systems with better locks, and an alarm system that keeps malicious crooks out.

How To Implement This Security Measure

Always protect your code base with protections notices and agents.md files with broad protection for your entire code. If you already done this; follow these steps:

1. Go to Google AI Studio.
2. Go to “My Apps”.
3. Open Your game/app what you are still working on or updating

4. Copy the following prompts:

   <br /> Create a honeypot folder outside of “src/” folder.<br /> Create “Name_Your_Honeypot_Folder/data.tsx” with its own “src/” folder inside, and make a lightweight mirrored version of this game.<br />

   Use this prompt to begin the process of making this honeypot folder above.

   Rename this folder name with your liking. You can replace “O” with “0”, and replace “l” with “1” just like how you use a typewriter. You can use capital letters and numbers and using dashes or underscores as a way to build this honeypot. This intentional typo system is ideal.

   You can also invert letter selection by reversing the alphabet order, or you can replace some letters with numbers.. for this instance; you can use “6” for “b” “9” for “g”; “8” for “B” as a way to build this honeypot folder.

   <br /> Create a zip folder with a full mirrored source code, and add _Wildcard_/data.tsx folders with 10 levels deep. Number the folders from 0 to 9.<br /> Also, create 2,000-line code files inside.<br />

   This is very important because, that will serve as a trap for these malicious scrapers, pruners, modifiers, refactoring processes, and other malicious processes via background.

   Use this boilerplate below:

   <br /> Create the following folders inside these honeypot folders by filling the “src/” folder using the lightweight system:<br /> System/ contains the following below:<br /> TPM/<br /> Visuals/<br /> Visuals/Animations/<br /> Sound/<br /> AI/<br /> Building_Blocks/<br /> Registry/<br /> UI/<br /> UI/Landing_Page/<br /> UI/Play_Area/<br /> Items/<br /> Items/Objects/<br /> Index/<br /> Engine/<br /> Index/Engine/<br /> Index/Game_Boot/<br /> Populate the root “src/” folder with app.tsx, and main.tsx,–and index.html. Also add CSS/data.css<br /> data.css is required for these honeypot systems<br /> Create a zip file that has a matrix of 200 deep folders with a depth of 200 folders inside.<br />

   *With this boilerplate above; you can customize how you want this system to be. Always start with these recommended folders first.

5. Send the prompt.
6. Update the honeypot on a regular basis,–after you update your game/app.
7. Check your honeypot folders for possible activities.

Conclusion

Cybersecurity is very important as you build your game via Google AI Studio. This is key to protect your crafted works, crafted code, and more.

Without security measures; your game will be broken beyond recovery.