You can store and manage scripts in the Extensions > Bambda library tab. This enables you to organize your scripts for easy reuse across your Burp projects. To add scripts to the library either create and save your own or import them from our GitHub repository.
Scripts are listed in a table with the following information:
Name - The name of the script.
Function - The task that the script is designed to perform. For example, View filter or Custom column.
Location - The tool in Burp that the script is intended to be used in. For example, HTTP history or Logger.
Last modified - The time and date that the script was most recently saved to the library.
You can filter the table contents as follows:
Search the table - Click Search and enter an expression.
Filter the table - Click the Filter settings bar to open the Bambda library filter window. You can filter by Function and Location.
You can import script files that have been shared with you or downloaded from our Bambdas GitHub repository. For information on how to do this and how to keep your imported scripts up-to-date, see Importing scripts into your Bambda library.
Bambda scripts can run arbitrary code. For security reasons, please be cautious when using scripts from unverified sources.
You can create scripts directly from the Bambda library. For more information, see Creating scripts.
To share scripts with others, select scripts in the Bambda library, then click . They're exported as .bambda files.
Each file includes a unique ID, name, function, and location as metadata. Burp uses the unique ID to recognize and match scripts. It is important to preserve the unique ID when sharing your script, as this ensures consistency and prevents conflicts if the script is reimported.
You can perform the following actions on the scripts in your library:
Edit - Select the script that you want to edit, then click .
Copy - Select the script that you want to copy, then click .
Delete - Select the script that you want to delete, then click .
If a script in your Bambda library defines a scan check function, any edits you make to that script are also reflected in your custom scan checks library, under Extensions > Custom scan checks.