ProfessionalCommunity Edition

Importing Bambdas into your Bambda library

  • Last updated: February 13, 2025

  • Read time: 2 Minutes

You can import Bambda files into your Bambda library that have been shared with you or downloaded from our Bambdas GitHub repository. Once imported, Bambdas can be loaded and applied across Burp Suite.

Warning

Bambdas can run arbitrary code. For security reasons, please be cautious when importing Bambdas from unverified sources.

To import Bambdas into your Bambda library:

  1. Go to Extensions > Bambda library.

  2. Click Import. The Import Bambdas dialog opens.

  3. Select .bambda files or a folder containing .bambda files.

  4. Click Open.

Burp adds the selected files to your Bambda library. If you select a folder, Burp identifies any .bambda files within the folder and its subfolders and adds them to your library.

Importing the full GitHub repository

To quickly import all Bambdas from our GitHub repository:

  1. Download the GitHub repository as a ZIP file.

  2. Extract the ZIP file contents.

  3. In Extensions > Bambda library, click Import.

  4. Select the extracted folder containing the GitHub repository files.

  5. Click Open.

  6. Burp identifies all .bambda files in the folder and its subfolders and adds them to your library.

Updating your Bambdas

If your Bambdas have been modified outside Burp, you can re-import them. Burp gives you the option to replace existing Bambdas with the new versions.

Note

As Bambdas in our GitHub repository may be updated frequently, we recommend re-importing these regularly to keep your library current.

How Burp overwrites Bambdas

When a Bambda is created in or imported into Burp (version 2025.2 onwards), it's assigned its own unique ID. The unique ID isn't visible in Burp, but it acts as a behind-the-scenes mechanism to manage conflicts and synchronize Bambdas that are re-imported. If you export Bambdas from Burp, the unique ID is included in the metadata.

When you import a Bambda, Burp checks its unique ID to determine if a matching Bambda exists in your library. If the unique IDs match, you're given the option to overwrite the existing Bambda.

Note

All Bambdas in our Early adopter GitHub repository have a unique identifier, regardless of when they were created.

Was this article helpful?