[---

My Shodan API Key leaked! What should I do?

What is a Shodan API Key and how it is used?

A Shodan API Key is a unique identifier that allows developers to access the Shodan search engine's API, enabling them to search for specific devices, services, and vulnerabilities on the internet.

When it comes to the Shodan API Key, developers should be aware of the following main use cases:

Accessing Shodan Data: The API key is used to authenticate and access the Shodan database, allowing developers to retrieve information about devices, services, and vulnerabilities on the internet.
Automating Tasks: Developers can use the API key to automate tasks such as scanning for specific types of devices or vulnerabilities, monitoring changes in the internet landscape, and integrating Shodan data into their own applications or scripts.
Enhancing Security Practices: By utilizing the Shodan API key, developers can improve their security practices by identifying exposed services, misconfigurations, and potential attack vectors in their own infrastructure or that of their clients.

---]

[---

1. Code snippets to prevent Shodan API Key hardcoding using environment variables

Using environment variables for storing sensitive information like API keys, such as the Shodan API Key, is a secure practice for several reasons:

Environment variables are not hard-coded in the codebase, reducing the risk of exposure through source code leaks.
Environment variables are stored outside of the codebase, making it harder for attackers to access them directly.
Environment variables can be managed separately from the code and can be easily rotated or updated without changing the code itself.
Environment variables are specific to the environment in which the code is running, ensuring that the sensitive information is only accessible in the intended environment.

How to secure your secrets using environment variables

---]

[---

2. Code snippet to prevent Shodan API Key hardcoding using AWS Secrets Manager

Using AWS Secrets Manager to manage Shodan API Keys is a secure way to handle sensitive data. Here are code snippets in five different programming languages that demonstrate how to retrieve the Shodan API Key from AWS Secrets Manager.

---]

[---

3. Code snippet to prevent Shodan API Key hardcoding using HashiCorp Vault

Using HashiCorp Vault for managing Shodan API Keys is a great way to enhance security. Here are code snippets in five different programming languages for securely handling a Shodan API Key using HashiCorp Vault.

Remember to replace the VAULT_ADDR and VAULT_TOKEN with your Vault server address and authentication token. The snippets assume that the Shodan API Key is stored under the api_key field within Vault. The specifics of the Vault path and field names should be adjusted to match your Vault setup.

---]

[---

4. Code snippet to prevent Shodan API Key hardcoding using CyberArk Conjur

Using CyberArk Conjur to manage Shodan API Key is a secure way to handle sensitive data. Here are code snippets in five different programming languages that demonstrate how to retrieve the Shodan API Key from CyberArk Conjur.

---]

[---

How to generate a Shodan API Key?

To generate a Shodan API Key, follow these steps:

Sign in to your Shodan account or create a new account if you don't have one.
Once logged in, go to your account settings.
Find the section for API Access and click on it.
Generate a new API Key by clicking on the "Generate Key" button.
Copy the generated API Key and securely store it as it will be needed to access the Shodan API.

---]

[---

My Shodan API Key leaked, what are the possible reasons?

There are several reasons why a Shodan API Key might have been leaked:

Improper storage: If the API key is stored in a plaintext file or hard-coded in the source code, it can easily be leaked through version control systems or by unauthorized access to the codebase.
Weak access controls: If the API key is shared with too many individuals or stored in a location with lax access controls, it increases the risk of unauthorized access and potential leakage.
Phishing attacks: Developers may fall victim to phishing attacks where they unknowingly provide their API key to malicious actors, resulting in a leak.
Third-party breaches: If the API key is used in integrations with third-party services that experience a data breach, the key could be exposed.
Human error: Mistakes such as accidentally sharing the API key in public forums, code snippets, or documentation can also lead to leakage.

What are the risks of leaking a Shodan API Key

When it comes to secret management, it is crucial for developers to understand the risks associated with leaking a Shodan API Key. Here are some specific risks that developers should be aware of:

Unauthorized Access: If a Shodan API Key is leaked, unauthorized individuals may gain access to your Shodan account and potentially sensitive information.
Financial Loss: Leaking a Shodan API Key could lead to financial loss, as attackers could potentially use the key to make unauthorized purchases or incur charges.
Reputation Damage: A data breach resulting from a leaked API Key can damage the reputation of both the developer and the organization they work for, leading to loss of trust from customers and partners.
Legal Consequences: Depending on the nature of the leaked information and applicable laws, there could be legal consequences for the developer and their organization.

It is important for developers to implement strong security practices, such as securely storing and managing API Keys, regularly monitoring for any unauthorized access, and promptly revoking and replacing keys if they suspect a leak. By being proactive and vigilant in protecting sensitive information, developers can mitigate the risks associated with leaking a Shodan API Key.

---]

[---

Shodan API Key security best practices

Avoid embedding the secret directly in your code. Instead, use environment variables or secrets managers‍
Secure storage: store the Shodan API Key in a secure location, such as a password manager or a secrets management service.
Regular rotation: periodically rotate the API key to minimize the risk of long-term exposure.
Restrict permissions: apply the principle of least privilege by only granting the key the minimum necessary permissions.
Monitor usage: regularly check the usage logs for any unusual activity or unauthorized access attempts.
Implement access controls: limit the number of users who have access to the secret and enforce strong authentication measures.
Use a secrets manager: utilize secret management tools like CyberArk or AWS Secrets Manager for enhanced security.

By adhering to the best practices, you can significantly reduce the risk associated with Shodan API Key usage and improve the overall security of your Shodan API Key implementations.

Exposing secrets on GitHub: What to do after leaking Credential and API keys

---]

[---

Shodan API Key leak remediation: what to do

What to do if you expose a secret: How to stay calm and respond to an incident [cheat sheet included]

How to check if Shodan API Key was used by malicious actors

Review Access Logs: Check the access logs of your Shodan API Key account for any unauthorized access or unusual activity. Pay particular attention to access from unfamiliar IP addresses (if you haven’t set up a specific allow list) or at odd hours.
Monitor Usage Patterns: Look for anomalies in the usage patterns, such as unexpected spikes in data access or transfer.
Check Active Connections and Operations: Review the list of active connections and recent operations on your database. Unusual or unauthorized operations might indicate malicious use.
Audit API Usage: If possible, audit the usage of your API key through any logging or monitoring services you have integrated with Shodan API Key. This can give insights into any unauthorized use of your key.

---]

[---

Steps to revoke the Shodan API Key

Generate a new Shodan API Key:

Log into your Shodan API Key account.
Navigate to the API section and generate a new API key.

Update Services with the new key:

Replace the compromised key with the new key in all your services that use this API key.
Ensure all your applications and services are updated with the new key before deactivating the old one.

Deactivate the old Shodan API Key:

Once the new key is in place and everything is functioning correctly, deactivate the old API key.
This can typically be done from the same section where you generated the new key.

Monitor after key rotation:

After deactivating the old key, monitor your systems closely to ensure that all services are running smoothly and that there are no unauthorized access attempts.

---]

[---

How to understand which services will stop working

Inventory of services: keep an inventory of all services and applications that utilize your Shodan API Key.
Communication and documentation: Ensure that your team is aware of which services are dependent on the key. Maintain documentation for quick reference.
Testing: before deactivating the old key, test your services with the new key in a staging environment. This helps in identifying any services that might face issues post rotation.
Fallback strategies: Have a fallback or emergency plan in case a critical service fails after the key rotation. This might include temporary measures or quick rollback procedures.

In summary, the remediation process involves identifying potential misuse, carefully rotating the key, and ensuring minimal disruption to services. Being proactive and having a well-documented process can greatly reduce the risks associated with a compromised API key.

---]

[---

What about other secrets?

GitGuardian helps developers keep 350+ types of secrets out of source code. GitGuardian’s automated secrets detection and remediation solution secure every step of the development lifecycle, from code to cloud:

On developer workstations with git hooks (pre-commit and pre-push);
On code sharing platforms like GitHub, GitLab, and Bitbucket;
In CI environments (Circle CI, Travis CI, Jenkins CI, GitHub Actions, and many more);
In Docker images.

---]

payment_intent

nullable object

The PaymentIntent object for errors returned on a request involving a PaymentIntent.

Hide

Show

child attributes

CLIENT LIBRARIES

$ gem install stripe

STRIPE-RUBY

$ pip install stripe

STRIPE-PYTHON

$ composer require stripe/stripe-php

STRIPE-PHP

MAVEN
<dependency>
  <groupId>com.stripe</groupId>
  <artifactId>stripe-java</artifactId>
  <version>24.16.0</version>
</dependency>

GRADLE
compile "com.stripe:stripe-java:24.16.0"

STRIPE-NODE

$ npm install --save stripe

STRIPE-NODE

$ go get github.com/stripe/stripe-go/v76

STRIPE-NODE

$ nuget install Stripe.net

STRIPE-NODE

SHOW

This is placeholder code

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents