Skaner Podatności: poradnik i samouczek
Dziury, których naprawdę używają oszuści, znalezione przed nimi.
Poradnik wideo pojawi się wkrótce
Do tego czasu poradnik poniżej przeprowadzi cię przez każdy krok.
Na razie ten poradnik jest tylko po angielsku.
What it is
Vulnerability Scanner reads your scripts and tells you what someone with a cheat menu could actually do on your server: give himself money, use admin commands, spawn objects until the server crashes, or reach your database. You get a security score and a list ordered by what to close first, each item written as what a player could do. Then ORBIE can rewrite the file so your server decides instead of the player, and give it back ready to drop in.
Who it's for
- Server owners who bought or downloaded scripts and want to know if they are safe before going live.
- Anyone who has seen money, items or vehicles appear out of nowhere on their server.
- Script sellers who want to show buyers a clean result without sharing their code.
Before you start
- The scripts to scan: a
.zipof your resources, a whole folder (even your fullresources/folder), or single.luaand.jsfiles. - To let ORBIE close the holes: a THE ORB account and, for most fixes, credits. See pricing.
Scan your scripts
- 1
Open the scanner
Go to Vulnerability Scanner.
- 2
Drop your resources
Drag a
.zip, a folder or.luaand.jsfiles onto the box that says Drop your resources here, or use Choose .zip / files or Choose a folder. Several resources at once are fine. - 3
Wait a moment
Every script is read and checked for the ways players usually break a server. It takes seconds.
The scan happens entirely in your browser and is free. No file is sent anywhere unless you ask ORBIE to fix that file.
Only .lua and .js files and the resource manifests are read. The manifest tells the tool which scripts run on players' computers and which run on the server, which matters here: anything on the player's side can be changed by a cheater. Very large uploads stop being read at about 25 MB of code or 4,000 files.
Your last scan is kept on this device. After changing your scripts, use Re-analyze new version in the Scan section to scan them again.
Read the score and the list
At the top of the Issues section you see the Security score, from 0 to 100, with a one-line verdict:
| Score | What it says |
|---|---|
| 85 to 100 | Nothing obvious for a cheater to grab |
| 60 to 84 | There are gaps somebody could use |
| 35 to 59 | A cheater will find these |
| Under 35 | This is wide open |
Below it, the problems are grouped by when to deal with them: Fix this first, Fix this soon, Worth fixing, and Minor. Each line says what a player could do, followed by the resource it is in.
The viewer opens on What someone could do to your server right now: the three worst problems. Click any of them to open it.
What it looks for:
- A player with a cheat menu can give himself unlimited money, or money and items are handed out by the player's own game instead of your server.
- A player can tell your server what something costs.
- Someone can wipe your entire database (SQL injection: text from a player goes straight into a database query).
- Someone can run their own code on your server, or commands on the machine it is hosted on.
- A password or key written into the script, readable by anyone with the files.
- Any player can use admin commands, because the check happens on the player's side.
- A player can rob or loot something from anywhere on the map.
- A player can spawn vehicles or objects until the server crashes.
- A player may be able to make your server send web requests anywhere they choose.
At the bottom of the overview, What we counted while scanning shows the raw numbers: lines of code, actions players can trigger, database calls, calls to outside services, passwords and keys in the code, and files scanned.
Open a problem
- 1
Click a problem in the list
The viewer shows its urgency, what a player could do, and when.
- 2
Read What needs to change
A short description of the change, written so you can judge afterwards whether ORBIE's fix did it.
- 3
Open See the technical details if you need them
The file and line, whether it runs on the player's computer or the server, the code that triggered it, and the technical explanation. Useful for a developer.
- 4
Go back
Use Back to the summary in the viewer's top bar.
Let ORBIE close one hole
Every problem has an ORBIE box with its price in the corner. The price depends on how much reasoning the fix needs: exact changes that need no AI are free, the rest cost a few credits (by default 1 or 5). Most security fixes need judgement. On the Free plan, the deeper fixes include one free try; after that they come with a paid plan.
- 1
Press Fix it, ORBIE
That file is sent to our server, plus its other half (the client or server file of the same resource) so ORBIE sees both sides of the exchange. It only happens when you click, and the code is not kept. You must be signed in.
- 2
Read the answer
You see How sure ORBIE is as a bar with a percentage, and What I changed in plain words. See exactly what changed opens the lines before and after.
- 3
Press Use this fix
The fix is applied to the copy kept in your browser, the file is checked again, and the score goes up if the hole is closed. Your files on disk are never touched.
ORBIE only offers Use this fix when it is sure enough (the minimum is shown on screen). If it cannot make a fix it trusts, it says why. When it actually ran and produced nothing safe, 1 credit is kept for the try; otherwise you are not charged. Kinds of problems marked ORBIE doesn't fix this one on its own yet are not offered at all.
Fix all of it
- 1
Check the total
At the bottom of the Issues section, the panel says how many problems ORBIE can fix and the exact total in credits, next to your balance. If your credits do not cover everything, it says roughly how many they reach.
- 2
Press Fix all of it
ORBIE works through the list, one fix and one charge at a time. A banner shows how many are fixed and skipped.
- 3
Leave if you want
It keeps working if you go to another page. The chip in the top bar brings you back. Press Stop to end it early.
It stops when your credits run out. What it fixed stays fixed.
Ask ORBIE to double-check
Some problems depend on what the rest of the script does: for example, a check may exist further down the file. When the list has any of those, a box offers Have ORBIE double-check these.
- 1
Press Review
ORBIE reads the code around each of those problems (up to 20). That part of each file is sent to us. It costs 1 credit by default, shown in the box.
- 2
See what changed
The ones that turn out to be fine are removed from the list and the score is recalculated. A line says how many were dropped.
Download or share the report
The Report section has three things:
- Download the PDF report: a branded PDF with the score and every problem, made in your browser. Keep it private: it says where each hole is.
- Share: publishes a public link at
/report/<code>and copies it. You must be signed in. The public page only shows the score, how many problems of each urgency, the framework and the kinds of problems. It never shows file names, lines or code, so nobody can use it to find the hole. - What ORBIE changed: every fix applied, with the lines it touched.
Check for lag in the rail sends the same upload to the Script Optimizer, so you do not have to drop it again.
What you download
After applying fixes, press Fixed files in the panel. You get <name>-fixed.zip with:
- Only the files ORBIE changed, each at the same path it had in your upload. Files nobody touched are not in the zip.
ORBIE-CHANGES.md: every fix applied, the file, the lines and what changed.
The PDF report downloads as <name>-security-report.pdf.
Install it on your server
- 1
Back up the resource
Copy the resource folder somewhere outside
resources/. - 2
Copy the fixed files over the originals
Unzip the download. Each file sits at the same path as in your upload, so copy it into the same place inside your resource, replacing the old one.
- 3
Try it on a test server first
Restart the server, or type
ensurefollowed by the resource name in the console. Use the feature that was fixed (the shop, the job, the robbery) and check it still works for an honest player. - 4
Move passwords and keys out
If the scan found a password or key in the code, change that password or key where it was issued as well. Anyone who had the old files already has it.
Keep your backup until you have tested the change. If anything misbehaves, put the original file back.
Common problems
The report is the same after I changed my scripts.
You are looking at the scan kept from before. In the Scan section, use Re-analyze new version and choose the new files, or New scan to start clean.
Fix it, ORBIE opens the plans window.
That problem needs a deep fix, and on the Free plan you already used your free one. See pricing.
ORBIE answered, but there is no Use this fix button.
ORBIE was not sure enough to hand you the file. Use its explanation and What needs to change to fix it by hand, or pass it to a developer.
It says it already tried this one twice.
A third try will not go differently. Use the explanation to fix it by hand.
After the fix, honest players cannot use the feature.
The server now checks something the player used to decide alone, such as distance or price. Put the original file back and have a developer look at the change in ORBIE-CHANGES.md.
My big upload seems to be missing scripts.
Reading stops at about 25 MB of code or 4,000 files. Scan fewer resources at a time.
Questions
Is my code uploaded?
Not to scan it. A file is sent to our server only when you ask ORBIE to fix or double-check it, and the code is not kept.
Does a high score mean nobody can cheat on my server?
No. It means none of the known patterns were found in what you scanned. Scripts you did not upload, escrow-protected scripts and your server's own settings are not covered.
Is the shared link safe to post publicly?
Yes. It shows the score and counts only, never the files, lines or code.
Can I scan escrow-protected scripts?
Their code is encrypted, so there is nothing readable to check.
Should I also run the Script Optimizer?
It answers a different question: what will lag your server. Use Check for lag to send the same upload there.
Checked against the tool on November 15, 2026.
Wypróbuj Skaner Podatności teraz
Przeskanuj swoje zasoby pod kątem dziur, których naprawdę używają oszuści: zdarzeń ufających klientowi, wstrzyknięć SQL i wyciekniętych kluczy.
