← Back to report

Investigate Hardcoded credentials in a URL

Build 1.18.2 · Scan 2026-10-03T23:15:27.306Z

2 distinct recorded findings; 2 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_config.arm64_v8a/lib/arm64-v8a/libgojni.so

Recorded match

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

Detector rule

basic_auth_url

Recorded file locations

• _split_config.arm64_v8a/lib/arm64-v8a/libgojni.so