Verilay Report
Analyse your own app →
Free scan report · GitHubA quick check, with a fix prompt for the most serious problem
juice-shop/juice-shop
Scanned 31 Oct 2026, 14:26 UTC (same code, reused analysis)
OWASP Juice Shop, an intentionally insecure Node.js/Angular web application used for security training and CTF challenges.
Not Ready
Fix the critical findings below before launching with real users.
IT Review Pack → a printable checklist for IT teams approving this app
D
Score
3
Critical
27
Warnings
6 of 6
Areas checked
What we found, by area
Authwarning
💡 Like a festival wristband checked at each stage gate, so only ticket holders get backstage.
Login uses JWT tokens and two-factor codes via otplib, with access rules set per route, though the JWT library is an outdated 0.4.0 version.
Outdated JWT library in use — package.json pins jsonwebtoken to 0.4.0, a very old release with known weaknesses in token verification.
💡 Key concept: Keeping the ticket-checking library current is as important as the locks themselves.
Configcritical
💡 Like a bakery writing its secret sourdough starter recipe on the front window for passersby to copy.
A private cryptographic key is stored in plain text in committed infrastructure and source files.
Private keys stored in source files — The secret scanner confirmed private key blocks in infrastructure/terraform/networking.tf (line 171), lib/insecurity.ts (line 21) and terraform/networking.tf (line 171).
💡 Key concept: Secrets belong in a locked safe outside the code, never on the shop window.
Databasewarning
💡 Like a restaurant's order ticket rail, where every table's order is pinned in sequence for the kitchen.
The app uses a local SQLite file database managed through Sequelize, with user passwords and TOTP secrets excluded from the auto-generated API.
Database file stored inside the app folder — The database lives at data/juiceshop.sqlite within the project, so it is copied and shipped with the code.
💡 Key concept: Where your data sits matters as much as who is allowed to read it.
APIwarning
💡 Like an airline dispatcher who takes requests from pilots and only hands out flight plans to those with the right badge.
The Express server exposes many REST endpoints with a mix of authorization checks, but several are deliberately open or unauthenticated.
Several endpoints intentionally lack authorization — Routes such as /rest/products/search and /api/Deliverys are registered without isAuthorized middleware; combined with intentionally vulnerable test code, several data paths are reachable by anyone.
💡 Key concept: Every request should be checked to confirm the person asking is allowed to see or change that data.
Frontendno issues seen
💡 Like the reading room in a library, where visitors see only the books the staff choose to put on display.
The Angular frontend is a standard single-page application with no obvious secret exposure in the reviewed files.
No critical frontend issue in reviewed files — The reviewed frontend files load scripts and styles normally and contain no hardcoded credentials.
💡 Key concept: The browser code is visible to everyone, so it must never hold secrets.
Librarieswarning
💡 Like a builder hiring specialist subcontractors, where each one's shoddy work can still affect the whole house.
The OSV.dev check found 20 of 170 directly installed packages with known vulnerabilities, including 3 serious ones.
20 directly installed packages have known security problems — The free check found 20 packages with 46 known advisories: 3 serious and 17 less severe. Only the 170 packages installed directly were checked; packages those depend on were not checked, because no full package list was found in the files reviewed.
💡 Key concept: Outside code must be kept up to date, because publicly known flaws are easy for attackers to find.
Verified Findings
Show all 30 ↓
Private Key File — infrastructure/terraform/networking.tf line 171
A private key is stored in your code. This is the digital equivalent of committing your house keys.
Private Key File — lib/insecurity.ts line 21
A private key is stored in your code. This is the digital equivalent of committing your house keys.
Private Key File — terraform/networking.tf line 171
A private key is stored in your code. This is the digital equivalent of committing your house keys.
JSON Web Token — frontend/src/app/app.guard.spec.ts line 46
A login token is written into your code. These are meant to be short-lived, not stored.
JSON Web Token — frontend/src/app/last-login-ip/last-login-ip.component.spec.ts line 72
A login token is written into your code. These are meant to be short-lived, not stored.
JSON Web Token — frontend/src/app/last-login-ip/last-login-ip.component.spec.ts line 78
A login token is written into your code. These are meant to be short-lived, not stored.
Generic Hardcoded Secret — test/api/2fa.test.ts line 42
Something that looks like a password or key is typed directly into your code.
Generic Hardcoded Secret — test/api/2fa.test.ts line 66
Something that looks like a password or key is typed directly into your code.
Generic Hardcoded Secret — test/api/2fa.test.ts line 85
Something that looks like a password or key is typed directly into your code.
Generic Hardcoded Secret — test/api/2fa.test.ts line 104
Something that looks like a password or key is typed directly into your code.
Generic Hardcoded Secret — test/api/2fa.test.ts line 123
Something that looks like a password or key is typed directly into your code.
Generic Hardcoded Secret — test/api/2fa.test.ts line 142
Something that looks like a password or key is typed directly into your code.
Generic Hardcoded Secret — test/api/2fa.test.ts line 182
Something that looks like a password or key is typed directly into your code.
Generic Hardcoded Secret — test/api/2fa.test.ts line 214
Something that looks like a password or key is typed directly into your code.
Generic Hardcoded Secret — test/api/2fa.test.ts line 240
Something that looks like a password or key is typed directly into your code.
Generic Hardcoded Secret — test/api/2fa.test.ts line 257
Something that looks like a password or key is typed directly into your code.
Generic Hardcoded Secret — test/api/2fa.test.ts line 266
Something that looks like a password or key is typed directly into your code.
Generic Hardcoded Secret — test/api/2fa.test.ts line 292
Something that looks like a password or key is typed directly into your code.
Generic Hardcoded Secret — test/api/2fa.test.ts line 317
Something that looks like a password or key is typed directly into your code.
Generic Hardcoded Secret — test/api/2fa.test.ts line 352
Something that looks like a password or key is typed directly into your code.
Generic Hardcoded Secret — test/api/2fa.test.ts line 379
Something that looks like a password or key is typed directly into your code.
Generic Hardcoded Secret — test/api/2fa.test.ts line 412
Something that looks like a password or key is typed directly into your code.
JSON Web Token — test/api/user.test.ts line 280
A login token is written into your code. These are meant to be short-lived, not stored.
JSON Web Token — test/cypress/e2e/forgedJwt.spec.ts line 22
A login token is written into your code. These are meant to be short-lived, not stored.
JSON Web Token — test/cypress/e2e/forgedJwt.spec.ts line 38
A login token is written into your code. These are meant to be short-lived, not stored.
Generic Hardcoded Secret — test/cypress/e2e/totpSetup.spec.ts line 7
Something that looks like a password or key is typed directly into your code.
JSON Web Token — test/server/currentUser.unit.test.ts line 31
A login token is written into your code. These are meant to be short-lived, not stored.
JSON Web Token — test/server/currentUser.unit.test.ts line 34
A login token is written into your code. These are meant to be short-lived, not stored.
JSON Web Token — test/server/verify.unit.test.ts line 308
A login token is written into your code. These are meant to be short-lived, not stored.
JSON Web Token — test/server/verify.unit.test.ts line 316
A login token is written into your code. These are meant to be short-lived, not stored.
Check it yourself · about 5 minutes
Is a secret saved in your GitHub repository?
  1. Open your repository on GitHub.
  2. Open the file and line that Verilay named in this report.
  3. Decide whether the value is real, or an example or placeholder.
✓ It's an example, a placeholder, or a value that is meant to be public.
⚠ It's a real key. Make a new key in the service's dashboard and switch to it. Deleting the file isn't enough, because the old key stays in the repository's history.
Never paste a real key into a chat, an email or a website while checking.
Is that login token real?
  1. Open the file Verilay named, on GitHub.
  2. Decide whether the value is a test or example, or came from a real logged-in account.
✓ It's a test or example value.
⚠ It's from a real account. Remove it, sign that account out everywhere and change its password.
Never paste a real token into a chat, an email or a website while checking.
Only try this on your own app, with test accounts. Never on someone else's app.
Worth A Look
A pointer, not a confirmed problem. It does not change your grade.
Worth a look: An old hash (MD5 or SHA-1) is used, and this app also handles passwords
lib/insecurity.ts line 41 hashes with MD5 or SHA-1, which are broken for protecting passwords. The app also appears to hash or check passwords (models/user.ts line 73). Verilay can't tell whether the two are connected, so this is a pointer to check, not a confirmed problem.
What to do: Check what that hash is used for. If it protects passwords or login tokens, replace it with bcrypt, scrypt or argon2. If it is only a cache label, you can ignore this.
Check it yourself · about 5 minutes
What is that old hash used for?
  1. Open the file Verilay named, on GitHub, and read the few lines around that hash.
  2. Ask your AI builder: "Is this hash used for passwords or login tokens anywhere? Review and advise, don't change anything yet."
  3. Read its answer.
✓ It's only used for labels, such as cache keys or file names.
⚠ It protects passwords or login tokens. Move to bcrypt, scrypt or argon2.
If you use a login service such as Supabase Auth or Clerk, your app may not store passwords at all.
Only try this on your own app, with test accounts. Never on someone else's app.
20 dependencies have known vulnerabilities
Checked 170 packages you installed directly against OSV.dev.
The packages these depend on were not checked, because no full package list was found in the files Verilay read.
Two ways to fix this: ask your AI builder to investigate (the “Ask AI” box just below can explain it in plain English), or skip the investigation: the deep scan hands you the exact package names, versions, and fixes already found.
Check it yourself · about 3 minutes
Do your packages have known problems?
  1. On GitHub, open your repository and click Security, then Dependabot alerts. It's free; if it's switched off, it can be turned on under Settings, then Security.
  2. Or ask a developer friend to run the free command npm audit in your project folder.
✓ No high or critical alerts.
⚠ Alerts are listed. Update the packages they name, then scan again.
Updating a package can break an app, so update one at a time and test after each.
Only try this on your own app, with test accounts. Never on someone else's app.
Fix these first
Copy a prompt, paste it into your AI builder (Lovable, Replit, Bolt, Cursor…), then re-run Verilay to check it worked. Treat each one as something to verify, not an order: your AI builder knows your code.
1. Private keys stored in source filescriticalConfig
Private key blocks committed to the repo (infrastructure/terraform/networking.tf line 171, lib/insecurity.ts line 21, terraform/networking.tf line 171) mean anyone with repo access can impersonate services or decrypt traffic. Once in git history, they stay exposed even if deleted.
How: 1. Confirm each flagged block is a real key and not a documented test fixture. 2. Search the whole repository (and git history) for other PEM/private key blocks, not only these files. 3. Check whether any of these keys are used in deployed infrastructure, and plan rotation if so.
Effort: 30 minutes
Step 1: paste this into your AI builder. It explains the problem first and changes nothing.
I received a security review flagging private keys stored in source files, specifically in infrastructure/terraform/networking.tf (line 171), lib/insecurity.ts (line 21) and terraform/networking.tf (line 171). Please review and advise without making changes yet. For each flagged location, explain what the key is used for and whether it is a deliberate test fixture or a real credential. Then check the ENTIRE repository, not only these files, and for EVERY file containing a PEM or private key block, list the file and line and whether it is referenced by any running configuration. Also check git history for previously committed keys. Advise what you find and suggest the minimal safe change (moving keys to environment variables or a secrets manager, and rotating any real keys) only if genuinely needed. Please don't change anything yet. In plain English, tell me: 1. Is this really a problem? Show me the exact file and lines. 2. Who could misuse it, and what could they see or do? 3. How is this part meant to be used? What relies on it working the way it does now: other pages, a mobile app that is already released, scheduled jobs, webhooks, emails, payments or sign-in? 4. What could the fix break, and how would we avoid that? 5. How will we check afterwards that everything still works, on the website and in the mobile app if there is one? Also check the whole app for the same kind of problem, and list every place with the file and line. Don't change anything until I reply.
Step 2: only when its answer makes sense to you, paste this to let it make the change.
Thanks. Please fix only the place named in this report, not the other places you listed: we'll do those separately, one at a time. Keep everything you listed working. Don't publish or deploy anything. I'll test it in the preview first. Then tell me exactly what you changed, file by file, and walk me through the checks from your answer so I can confirm everything still works. If there's a mobile app that's already released, remind me to test it after publishing.
Check it yourself · about 3 minutes
Is a secret saved in your GitHub repository?
  1. Open your repository on GitHub.
  2. Open the file and line that Verilay named in this report.
  3. Decide whether the value is real, or an example or placeholder.
✓ It's an example, a placeholder, or a value that is meant to be public.
⚠ It's a real key. Make a new key in the service's dashboard and switch to it. Deleting the file isn't enough, because the old key stays in the repository's history.
Never paste a real key into a chat, an email or a website while checking.
Only try this on your own app, with test accounts. Never on someone else's app.
More fix prompts with Verilay Pro
This free scan includes a fix prompt for the most serious problem. Verilay Pro gives a ready-to-paste fix prompt for every finding: free until 30 November (4 quick questions on the Pricing page, no card needed), then A$4.99 a scan. See Verilay Pro
💬 Ask Verilay about your report
Plain-English answers about your results. Tap a question or type your own.
Or open Claude with my findings →
Compared with your earlier scan (31 Oct 2026, 14:26 UTC, grade D).See the comparison →
More details: scan stats, tech stack, how your app fits together, similar projects, second opinions
Scan At A Glance
What was checked
AI code review
25 of 1,172 files (2%)
Secret scan
All 1,172 files
Weak-crypto scan
All 1,172 files · 1 to check
Dependencies
170 packages · 20 vulnerable packages
Access rules (Supabase)
Not applicable, no Supabase database files found
Dependencies: 170 packages you installed directly. The packages these depend on were not checked, because no full package list was found in the files Verilay read.
Health by area
Auth · warningConfig · criticalDatabase · warningAPI · warningFrontend · no issues seenLibraries · warning
Known issues in your packages (20)
critical (3)lower (17)
What it is made of (1,172 files, every file in the repository)
Logins and data (295)Pages and visuals (182)Settings (205)Bundled libraries (1)Everything else (489)
Estimated time for the 1 priority fix above: about 30 minutes. These are the AI's own estimates, not a promise, and package updates are extra.
Tech Stack
Express ^4.22.1Angular ^22.0.1Sequelize ^6.37.3sqlite3 ^5.1.7jsonwebtoken 0.4.0Socket.IO ^4.8.4
How Your App Fits Together
OWASP Juice Shop, an intentionally insecure Node.js/Angular web application used for security training and CTF challenges.
Shop StorefrontFRONTENDIt shows products, lets…Shop RecordsDATABASEStores users, products,…Member LoginAUTHHandles sign-in, issues…Shop RequestsAPIIt handles logins,…Shop Building PartsLIBRARIESThey handle the web server, database access, login tokens, file…App SecretsCONFIGHolds server settings,…
What each part does
Shop StorefrontFRONTEND
It shows products, lets people log in, fill a basket, and leave reviews.
Shop RequestsAPI
It handles logins, baskets, orders, product reviews, and user profiles for this shop.
Member LoginAUTH
Handles sign-in, issues JWT tickets, checks two-factor codes, and blocks unauthorized access to routes like baskets and user records.
Shop RecordsDATABASE
Stores users, products, baskets, orders, feedback and payment card records in a single SQLite file.
App SecretsCONFIG
Holds server settings, the signing key used for login tickets, and infrastructure definitions for deployment.
Shop Building PartsLIBRARIES
They handle the web server, database access, login tokens, file uploads, and visual styling.
Files reviewed: 25 of 1172
The free analysis covers the 25 files most likely to carry risk. Want more files reviewed, plus exact dependency package names and fixes? See the deep scan.
Closest open-source match
A project that appears to do a similar job. Category: web security training. Worth a look before you build more of the same, or to see what you could learn from or reuse.
webpwnized/mutillidae  updated 1 months ago · GPL-3.0 · PHP
OWASP Mutillidae II is a free, open-source, deliberately vulnerable web application providing a target for web-security training. This is an easy-to-use web hacking environment designed for labs, security enthusiasts, cl
Similar: Both are deliberately vulnerable web apps covering OWASP Top 10 for security training and labs.
4 more similar projects are listed in the deep scan.
Tip: These matches come from free, open-source projects on GitHub only. Commercial and closed-source apps are not included, so few or no matches does not mean nothing similar exists. Check a project's licence before reusing any of its code.
Your app is large (about 78,238 lines). Big apps get slower and costlier for an AI builder to change. A deep scan includes a code fitness check: whether yours needs tidying at all, and why.
Scores may vary slightly between runs as findings are AI-generated. A meaningful improvement (e.g. C → B) after applying fixes indicates real progress.

AI disclaimer: Analysis is generated by Claude AI and may contain false positives or miss issues. Always verify findings with your AI builder before making changes. This is not a professional security audit. See full terms.