Security
Security and code audit of an inherited platform
When a client took over a platform built by a previous team, we audited its code and security to find exactly what was wrong before anyone built anything new on top of it.
A full security and code audit of an inherited marketplace platform across five codebases. It found 92 issues, 28 of them critical, before anything new was built on top, and ordered the fixes so the most dangerous close first.
- Code audit
- Secret scanning
- Endpoint auth map
- Dependency scan
- Remediation plan
- Semgrep
- Gitleaks
- npm audit
- Endpoint auth mapping
- AI-assisted review
- Remediation planning
Before
A marketplace came to its new owners running on a platform built by a previous team, with no clean handover and real questions about how safely it handled customer data. Building new features on an unknown foundation would only deepen the risk. The responsible first move was to find out exactly what was there. We audited the whole platform so the owners knew precisely what they had inherited and what to fix first.
What made it hard
The platform was already live with real users, so the audit had to assess it without disrupting the running business.
The code arrived with no documentation, spread across five codebases: a backend, a web app, an admin panel, a mobile app, and an archived site.
Automated scanners miss the most dangerous issues, which hide in how the pieces fit together, so scanning had to be paired with analysis of the code itself.
The output had to be honest and prioritized, so the owners could close the most dangerous problems first.
What we built
Audited all five inherited codebases with eleven parallel analysis passes, combined with secret scanning, dependency scanning, and static analysis.
Mapped all 312 API endpoints and found 68 missing required login checks and 27 more relying on optional ones.
Surfaced the critical classes: live credentials committed in source, injectable database queries, payment webhooks accepted without a signature check, and weak, unsalted password hashing.
Reconciled the results against an earlier outside audit: 40 of our 92 findings were new.
Delivered a remediation plan with a timeline and resourcing, ordered so the most dangerous issues close first.
Results
Backend, web app, admin panel, mobile app, and an archived site, across eleven parallel analysis passes and three scanners.
Out of 92 in total, 40 of them missed by an earlier outside audit. Each one came with a fix and a priority.
Including every critical one, tracked finding by finding in the rebuilt codebase.
Where it stands
Delivered in March 2026. The fixes are being made as part of the platform rebuild.
