In most cases, trust boundaries are violated when a secret is exposed in a source code repository or an uncontrolled deployment environment.
Unintended people who don’t need to know the secret might get access to it. They might then be able to use it to gain unwanted access to associated
services or resources.
The trust issue can be more or less severe depending on the people’s role and entitlement.
What is the potential impact?
If a Shippo API token is leaked, it can have several consequences:
Financial Loss
If the leaked API token is used to generate shipping labels or make shipping-related transactions, it can result in financial loss. Unauthorized
individuals may exploit the token to generate fraudulent labels or make unauthorized shipments, leading to additional shipping costs or potential
chargebacks. ==== Data Breach
If the leaked API token is associated with a user account that has access to sensitive customer or business data, it can result in a data breach.
This can lead to the exposure of personal information, shipping addresses, payment details, or other confidential data, potentially causing harm to
your customers and your business reputation.
