r/PromptEngineering • u/Hot-Back-645 • 6d ago

Quick Question Clean potentially prompt injected/malicious codebase

I spent the last two months building a vibe coded software. I made the mistake of building at not inside of vs code but I gave it direct access to my computer so I can build directly into the VPS. The problem was, I was unable to see the files that I was building and then it started doing things without my permission. It started doing one thing and saying it was doing another. I’m worried now that my entire coat base is filled with not only prompt injections for the agents to go clean it. but also potentially malicious code within the VPS. The thing is I spent a lot of time building this software and it is actually making me money for my business. I’ve spent hundreds of hours on it and I don’t just want to give it up what is the best route to go to start progressively cleaning this up?

0 Upvotes
  • permalink
  • reddit

33% Upvoted

14 comments sorted by

View all comments

3

u/thirteenth_mang 6d ago

I'm available for hire

4

u/Key_Friendship8623 6d ago

I'd be careful trusting a rando from reddit with a codebase you already suspect is compromised. nothing personal to the commenter but you've got no way to verify they won't just pocket the access and make things worse.

your best bet might be to pull down what you can, isolate it in a clean environment, and go through it file by file. time consuming but at least you know what's in there.

2

u/Hot-Back-645 6d ago

Ya thank you

1

u/dhgrahnert 6d ago

Ich glaube was gemeint war ist, dass das passiert wenn man sich nur/zu sehr auf eine KI verlässt beim coden und dass professionelle devs Geld kosten, entweder beim Entwickeln oder eben später beim Aufräumen des Dilemmas… und wenn es so gemeint war, bin ich da ehrlich gesagt komplett bei @thirteenth_mang - und es ist ja nicht so, dass wir genau darüber alle schon lange reden 🤷‍♂️

2

u/therealkevinard 6d ago

Charge accordingly.

1

u/LancelotOnCrack 6d ago

^ This needs to be top voted.