← Back to report

Investigate Hardcoded credentials in a URL (third-party library artifact, shared across 6 unrelated developers)

Build 6.0.7 · Scan 2026-10-11T21:18:45.819Z

1 distinct recorded findings; 1 have inspectable metadata. Locations are representative, not an inventory of every source match.

A username and password are embedded directly in a URL inside the app. If that host is reachable, this is a hardcoded credential and should be rotated. Confirm it isn't a placeholder/example first.

Static evidence does not establish runtime impact. Source excerpts and line numbers were not recorded.

Evidence preview

Evidence type

Static string match

Representative location

assets/public/js/381059f2.libs.js

Recorded match

•••••••• (21–40 chars, redacted)

Detector rule

basic_auth_url

Recorded file locations

• assets/public/js/381059f2.libs.js