Skip to content

Generic Base64 Credentials

Service Name: Generic Base64 Authentication

Service Description: Base64 encoding is commonly used to encode binary data, including authentication credentials, into ASCII string format for transmission over protocols that only support text content. Generic Base64 credentials typically represent username:password combinations encoded in Base64 format, often used in HTTP Basic Authentication.

Service Address: Not specific to a single service - used across many web services and APIs

Validation Type: API Auth

IP Allow list: Does not exist at the credential level, but may be implemented at the service level depending on the specific service using these credentials

Secret Access Scope: Grants access to resources protected by Basic Authentication. The specific access level depends on the permissions associated with the encoded username and password.

Secret Revokement URL: Does not exist (depends on the specific service using these credentials)

Secret Example: dXNlcm5hbWU6cGFzc3dvcmQ= (Base64 encoding of "username:password")

Suspicious Activity Investigation Instructions:

  • Identify which service the Base64 credentials are being used for

  • Review access logs for the associated service to detect unusual access patterns

  • Check for unauthorized API calls or data access using these credentials

  • Monitor for unusual IP addresses or locations accessing the service

  • Verify if the credentials are being used outside expected applications or scripts

Mitigation Instructions:

  • Change the password for the account associated with the compromised credentials

  • Implement multi-factor authentication if available for the service

  • Rotate credentials regularly to limit the impact of potential exposure

  • Consider implementing IP restrictions at the service level if possible

  • Update any applications, scripts, or configuration files that use the compromised credentials

  • Review and update access control policies to follow the principle of least privilege

  • Consider implementing a secrets management solution to avoid hardcoding credentials