ProfessionalCommunity Edition

Managing custom scan checks in your library

Last updated: September 11, 2025
Read time: 3 Minutes

You can store and manage custom scan checks in the Extensions > Custom scan checks tab. This enables you to reuse your checks across your Burp projects. To add checks to the library you can create and save your own or import them from our GitHub repositories.

Custom scan checks are listed in a table with the following information:

Name - The name of the check.
Author - The author of the check.
Tags - Any tags that are applied to the custom scan check.

Note

The Tags and Author columns are only populated for custom scan checks written in the BChecks language. They are automatically populated from the definition. To modify them, edit the check's definition directly.

To search the table, enter text in the search bar. You can also customize and sort the table contents. For more information, see Customizing Burp's tables.

For instructions on how to use custom scan checks in your scans, see Adding custom scan checks to scans.

Importing custom scan checks

You can import custom scan checks that have been shared with you or downloaded from our Bambda scripts repository or BChecks repository. For more information, see Importing custom scan checks into your library.

Warning

Custom scan checks can run arbitrary code. For security reasons, please be cautious when importing and using scan checks from unverified sources.

Creating custom scan checks

You can create checks directly from the custom scan checks library. For more information, see Creating custom scan checks.

Exporting custom scan checks

You can export custom scan checks to import them into other instances of Burp.

To export checks:

In the library, select the checks you want to export.
Click Export .
Select a directory.
Save the checks to the directory:
- Single check: Enter a filename then click Save.
- Multiple checks: Click Save to export all selected checks into a folder. Each check is saved with its current name.

The checks are exported with the correct file extension:

.bcheck files for BCheck-based checks
.bambda files for script-based checks

Each .bambda file includes metadata (unique ID, name, function, and location). Burp uses the unique ID to match checks, so always preserve it when sharing to avoid conflicts.

Burp matches .bcheck files by filename, so keep filenames consistent when sharing.

For more information about how the unique ID is used when re-importing checks, see Importing custom scan checks - Updating your checks.

You can share your checks with the community by adding them to our ever-growing GitHub repositories.

For information on submitting script custom scan checks to our Bambda scripts GitHub repository, see Submitting scripts to our GitHub repository.

For information on submitting BCheck custom scan checks to our BChecks GitHub repository, see Submitting BChecks to the community.

For more information about our custom BCheck language, see BCheck definitions.