← Back to report

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

Build 1.18.157 · Scan 2026-10-10T08:58:37.192Z

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/fonts/en_a.ttf

Recorded match

•••••••• (40+ chars, redacted)

Detector rule

basic_auth_url

Recorded file locations

• assets/fonts/en_a.ttf