Project Lazarus ZOMBIES Kill All Zombies Script
Loop-kill families, lobby-only execute notes, and the gist loadstring for a basic hub.
Kill-all scripts are the blunt instruments of the Project Lazarus ZOMBIES executor scene: a loop that deletes zombies as they spawn, often bundled with infinite points and infinite ammo. They are not a 29-feature GUI. They are a farm. logitech101 still permanently bans exploiters, and this family is the one other players notice first — rounds end in seconds, nobody is shooting, and the scoreboard is nonsense.
Read the scripts hub first. If you want a toggle-heavy GUI instead of a loop, that is the SFG Feature Hub. This page is the loop-kill notes, the kick reports, a small open-source hub loadstring, and the Tapbound-style overlay family that sits next to kill-all in the same Discord threads.
Loop-kill / inf points / inf ammo
Community copies advertise the same three promises:
- Kill all / kill aura / loop kill — zombies die without a pellet. Some versions only strip health from zombies already on the map; others hook spawn so new ones never take a step.
- Infinite points — the HUD number stops being a budget. Doors, perks, the 950-point box, and the 5,000-point Pack-a-Punch become free, which also makes the points guide irrelevant for that session.
- Infinite ammo — no Max Ammo drops, no wall-buy refill. This is the hook that patches break most often, same as on SFG.
They skip every skill the rest of this wiki cares about: knife routing, round scaling, and how to train. A loop that “beats” round 50 is not a high-round; it is a disabled horde.
Community execute notes (and kicks)
Players who still share these scripts repeat two instructions:
- Execute in the lobby, during intermission, before the match starts. Attaching mid-round is blamed for missed hooks and for instant kicks.
- Do not shoot while some variants run. Firing a real gun while a kill loop is also writing to zombie health is the pattern people associate with detections. Other users say they could shoot anyway. Treat that disagreement as “this is unstable,” not as a technique to master.
Kick reports are mixed and public: some people get an instant kick, some play through Frontier-era builds, some get kicked later when a nuke or Carpenter tries to resolve against an empty zombie list. There is no version table that stays true for a week. After the Model 1887 update revive and perk-check work, assume any old loop needs a re-test and will probably error.
If the script starts dumping errors about nil instances, stop executing it. Spamming a broken loop is how you turn a kick into a ban report.
Open-source basic hub loadstring
A small keyless hub still circulates as a gist. It is not a full kill-all. Community notes call it a basic hub: do not expect SFG’s 29 features. It is useful as a known-raw example of the loadstring shape:
loadstring(game:HttpGet("https://gist.githubusercontent.com/reslavaa/2a5c750df37e3159744b727468d31560/raw/71d6f22ee754aa22e629d0c8163f104315956e76/gistfile1.txt"))()
If that URL 404s, the hub is gone. Do not replace it with the first “Project Lazarus OP” file in a random server. Keyless gists are easy to swap for malicious HttpGets that steal cookies instead of drawing a GUI.
Tapbound-style overlays
Another family shows up in the same threads: ESP on zombies, teleport to the Mystery Box, teleport to perk machines, insta-kill. Think of it as a map cheat plus a damage cheat, not a round-clear loop. PC support is mixed. Some builds attach on one executor and silently do nothing on another. Box TP and perk TP skip the 750–1,000 debris bills and the Graduation power-plus-key route; they also put you inside rooms the train on how to train never uses, which is an easy way to get cornered if the insta-kill toggle is off.
ESP alone is enough to get reported in a six-player lobby. Combining ESP with insta-kill is the same risk bucket as kill-all, just with more clicking.
Why this wiki still documents them
Squads ask whether a teammate is looping, whether a gist is “the kill all,” and whether they should run it on a throwaway. Answers: looping looks like rounds resolving with no gunfire; the gist above is a basic hub, not a guaranteed kill-all; throwaways still burn time and still leak if you reuse a main account’s email. logitech101’s ban is the published rule.
If the goal is actually rounds, close the executor. Open high-round strategy, buy four perks the honest way, and chase Frostbite on the weapon tier list. The scripts hub and SFG hub are the only other script pages; everything else on this wiki assumes you are firing the Beretta like a normal player.
Kill-all is the fastest way to see a high round number and the fastest way to lose the account that would have meant something. The lobby-execute warning is a kick-avoidance rumor, not a safety certificate.
Frequently Asked Questions
Quick answers for perks, Mystery Box pulls, and high-round survival.
Should I execute kill-all in the match?
Community notes say execute in the lobby and, on some variants, do not shoot while it runs. People still report instant kicks. There is no safe method.
Is the gist loadstring a full kill-all?
No. It is a basic open-source hub. Do not expect infinite points, and do not treat a 404 as a reason to paste a random replacement.
What is the Tapbound-style family?
ESP, box teleport, perk teleport, and insta-kill overlays. PC support is mixed. Same ban risk as loop-kill.
Will this survive Model 1887?
Many loops were already flaky. Revive and perk-check changes in the Model 1887 update are exactly the kind of patch that kills hooks.
Is logitech101 okay with farm scripts?
No. Permanent ban for exploiters is on the Roblox page. See the scripts hub.
What should I use instead?
Play legit: getting started, points, and high-round strategy.