Short answer: yes, with one asterisk that has nothing to do with viruses or bans. But "is it safe" is actually three questions wearing a trench coat, and people who ask it usually only mean one of them. Let me split them apart, because the honest answer to each is different.
- Malware? No. Antivirus flags are false positives — and I know exactly why.
- Bans? No. Borderlands 2 has no VAC and no anti-cheat. Nothing is watching your saves.
- The real risk? You, overwriting a good save with a broken one. Back up first and even that goes away.
The three questions hiding inside "is it safe"
When someone asks me this, they mean one of:
- Will this exe infect my computer?
- Will I get banned for using it?
- Will it wreck my save file — or get me in some kind of trouble?
Different fears, different answers. Mixing them is why the forum threads go in circles. Let me take them one at a time.
1. Will it infect my PC?
No. And I want to be precise here instead of just saying "trust me," because your antivirus is probably about to tell you otherwise.
Here's what's real: the genuine editor, downloaded from Gibbed's GitHub, is clean. The entire source code is public — anyone can read it, and people have. There's no payload in there. What there is, fairly often, is a false positive. Norton 360 is a repeat offender. You might see VirusTotal light up with a detection name like PE:Malware.RDM.32!5.26 from one or two no-name engines while the big ones stay silent. That pattern — a couple of obscure scanners flagging what everything else calls clean — is the signature of a false positive, not a real threat.
Why a clean tool trips the alarm
This isn't hand-waving; Gibbed answered it himself in the repo (issue #144). The editor is a .NET application. When a .NET app starts, the framework reaches out to Microsoft's own certificate servers to check signatures — totally routine, half the programs on your machine do it. But a heuristic scanner sees "tiny unknown executable, makes an outbound network call the second it launches" and decides that's suspicious. It isn't. It's just .NET being .NET.
Gibbed's own take on fixing it, paraphrasing his comments over the years: there's not much he can do except report the false positive to the AV vendor and get ignored. His standing offer to the paranoid is the right one — if you don't trust the prebuilt exe, grab the source and compile it yourself. The fact that he can say that, and mean it, tells you everything.
Add an exclusion for the editor's folder and you're done. But — and this matters — only do that for the file you got as the verified file — from the download here or the author's own release. Which brings me to the asterisk.
"It's a false positive" is true for the real file. It is not a blanket pass for any "gibbed.exe" you found on a random download site. Re-hosted, repackaged copies are precisely where actual malware likes to ride along — because nobody can eyeball a clean exe versus a poisoned one. If you skipped it, read how to download it safely first. The whole malware question evaporates the moment you pull it from the source.
2. Will I get banned?
No. This one's almost boring once you know the technical reason: Borderlands 2 is not a VAC-secured game. Valve Anti-Cheat isn't running on it. There's no anti-cheat process scanning your saves, comparing your gear to a server, or reporting you anywhere. The mechanism that would issue a ban simply isn't there.
The community has been stress-testing this for over a decade. The recurring answer in every "is this bannable now?" thread is some version of "go hog wild, I still have my modded gear and no bans." The game's been out 14 years and stopped getting real updates ages ago. Nobody at Gearbox is hunting single-player save editors.
There's a footnote: an updated Terms of Service somewhere added vague language about "malicious mods or those that impact other players' experience." Technically that exists. Practically, enforcement on a dormant single-player-friendly game is nil. The takeaway isn't "they might ban you" — it's the etiquette rule below.
The one rule worth following: keep it offline-ish
The single piece of advice that actually has teeth has nothing to do with bans and everything to do with not being that guy. The community standard, stated bluntly in thread after thread: "just stay out of multiplayer with gibbed characters."
Why? Not because you'll get banned — because dropping an impossible, over-leveled, modded-parts weapon into a random stranger's game can flat-out crash their session or ruin the run they were enjoying. Among friends who know and don't care, do whatever you want. In a random public lobby, leave the obviously-fabricated gear at home. That's the whole etiquette. It's social, not technical.
3. Will it break my save? (the real risk)
Here's the asterisk. The only thing that genuinely goes wrong with Gibbed isn't the tool — it's you, editing a field you don't understand and hitting save over your only copy. I've done it. Years back I turned a 300-hour character into an unloadable file by getting greedy with values I didn't understand, and there was no undo button waiting for me.
The fix is stupidly simple and every veteran says the same thing: "backup your save folder before you use Gibbed. Just in case YOU make a mistake." Copy the folder somewhere safe before you touch anything. Then the worst case stops being "I lost my character" and becomes "I delete the broken file and paste the good one back." Five seconds of caution, total peace of mind.
Not sure what to back up or where it is? I walk through the exact folder and a 10-second backup in where Borderlands 2 keeps your saves.
Is it even legal?
For PC single-player: it's your save file, for a game you bought, edited on your own machine. You're not pirating anything and you're not cheating against other people. This isn't legal advice and I'm not a lawyer, but morally and practically it sits in the same bucket as using a trainer or a console command in a game you own — your sandbox, your rules.
The picture only changes on consoles, where "ban" becomes a real word again: re-injecting a modified save onto Xbox Live or PSN runs into those platforms' terms of service, and that's a genuinely different risk from PC. If that's your situation, the process and its caveats live on the platform pages — start at the error hub for the console save flow.
So, is it safe?
Yes. The malware scare is a false positive with a known, boring cause. The ban fear is moot because there's no anti-cheat to ban you. The only thing that can actually bite you is overwriting a good save with a bad edit — and a 5-second backup erases that too. Download it from the right place, copy your save folder, and go nuts.
Quick answers
Should I run it as administrator?
My antivirus already deleted it. What now?
Can it ban me from getting SHiFT codes / golden keys?
Is it safe on a pirated copy of the game?
Steam discussions "Is Gibbed save editor safe to use?" and "Is using Gibbed Bannable now?"; the Se7enSins "editor registering as virus" thread; Gibbed's own comments on the false-positive issue (issue #144 and blog); and a decade of community consensus. Checked June 2026.