← Back to report

Investigate Hardcoded credentials in a URL

Build 13.9.2 · Scan 2026-10-08T20:46:52.823Z

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

_split_default_asset_pack/assets/fonts/vllo_fonts/font_en_KomikaTitle-Tilt.ttf

Recorded match

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

Detector rule

basic_auth_url

Recorded file locations

• _split_default_asset_pack/assets/fonts/vllo_fonts/font_en_KomikaTitle-Tilt.ttf