Go to file
2024-06-21 08:09:53 +00:00
.devcontainer Add gh-cli, add extensions, node_modules as a volume 2024-02-17 10:06:19 +00:00
.github Remove specified permissions 2024-02-13 00:42:41 +00:00
src Merge pull request #1828 from robinsandhu/feat/support-other-keys-in-parse-csr 2024-06-21 09:00:12 +01:00
tests Merge branch 'master' into feat/support-other-keys-in-parse-csr 2024-06-11 22:51:32 +01:00
.dockerignore Add a .dockerignore file 2024-02-12 10:46:28 +00:00
.editorconfig Added nightwatch.js test suite for confirming that the app loads correctly and can run operations from each module. Currently only support the latest version of Chrome. 2018-12-29 02:58:05 +00:00
.gitattributes Add gh-cli, add extensions, node_modules as a volume 2024-02-17 10:06:19 +00:00
.gitignore Add support for LZNT1 decompression. 2023-12-25 23:06:11 +01:00
.npmignore Removed JSDoc generation as it is never really used. JSDoc comments are still required but the doc files will no longer be generated. This simplifies the build process and config scripts. 2019-08-28 16:37:31 +01:00
.nvmrc upgrade to nodejs v18 2022-07-14 14:27:59 +01:00
babel.config.js Updated to Node 17 2022-03-25 14:59:54 +00:00
CHANGELOG.md Bump to 10.19.0 2024-06-21 08:09:53 +00:00
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md 2017-06-16 15:32:55 +01:00
Dockerfile Switch to using Dockerfile 2024-02-12 10:46:28 +00:00
eslint.config.mjs Updated eslint, Jimp, and other dependencies 2024-06-11 18:07:22 +01:00
Gruntfile.js Updated eslint, Jimp, and other dependencies 2024-06-11 18:07:22 +01:00
LICENSE Initial commit 2016-11-28 10:42:58 +00:00
nightwatch.json Added more IO tests and created browser test utils 2023-03-05 14:58:11 +00:00
package-lock.json Bump to 10.19.0 2024-06-21 08:09:53 +00:00
package.json Bump to 10.19.0 2024-06-21 08:09:53 +00:00
postcss.config.js Updated dependencies 2019-06-27 17:29:27 +01:00
README.md Point to the correct workflow in the README for Container releases. 2024-02-12 10:46:28 +00:00
SECURITY.md Create SECURITY.md 2019-08-22 17:38:56 +01:00
webpack.config.js Updated eslint, Jimp, and other dependencies 2024-06-11 18:07:22 +01:00

CyberChef

npm Gitter

The Cyber Swiss Army Knife

CyberChef is a simple, intuitive web app for carrying out all manner of "cyber" operations within a web browser. These operations include simple encoding like XOR and Base64, more complex encryption like AES, DES and Blowfish, creating binary and hexdumps, compression and decompression of data, calculating hashes and checksums, IPv6 and X.509 parsing, changing character encodings, and much more.

The tool is designed to enable both technical and non-technical analysts to manipulate data in complex ways without having to deal with complex tools or algorithms. It was conceived, designed, built and incrementally improved by an analyst in their 10% innovation time over several years.

Live demo

CyberChef is still under active development. As a result, it shouldn't be considered a finished product. There is still testing and bug fixing to do, new features to be added and additional documentation to write. Please contribute!

Cryptographic operations in CyberChef should not be relied upon to provide security in any situation. No guarantee is offered for their correctness.

A live demo can be found here - have fun!

Containers

If you would like to try out CyberChef locally you can either build it yourself:

docker build --tag cyberchef --ulimit nofile=10000 .
docker run -it -p 8080:80 cyberchef

Or you can use our image directly:

docker run -it -p 8080:80 ghcr.io/gchq/cyberchef:latest

This image is built and published through our GitHub Workflows

How it works

There are four main areas in CyberChef:

  1. The input box in the top right, where you can paste, type or drag the text or file you want to operate on.
  2. The output box in the bottom right, where the outcome of your processing will be displayed.
  3. The operations list on the far left, where you can find all the operations that CyberChef is capable of in categorised lists, or by searching.
  4. The recipe area in the middle, where you can drag the operations that you want to use and specify arguments and options.

You can use as many operations as you like in simple or complex ways. Some examples are as follows:

Features

  • Drag and drop
    • Operations can be dragged in and out of the recipe list, or reorganised.
    • Files up to 2GB can be dragged over the input box to load them directly into the browser.
  • Auto Bake
    • Whenever you modify the input or the recipe, CyberChef will automatically "bake" for you and produce the output immediately.
    • This can be turned off and operated manually if it is affecting performance (if the input is very large, for instance).
  • Automated encoding detection
    • CyberChef uses a number of techniques to attempt to automatically detect which encodings your data is under. If it finds a suitable operation that make sense of your data, it displays the 'magic' icon in the Output field which you can click to decode your data.
  • Breakpoints
    • You can set breakpoints on any operation in your recipe to pause execution before running it.
    • You can also step through the recipe one operation at a time to see what the data looks like at each stage.
  • Save and load recipes
    • If you come up with an awesome recipe that you know youll want to use again, just click "Save recipe" and add it to your local storage. It'll be waiting for you next time you visit CyberChef.
    • You can also copy the URL, which includes your recipe and input, to easily share it with others.
  • Search
    • If you know the name of the operation you want or a word associated with it, start typing it into the search field and any matching operations will immediately be shown.
  • Highlighting
  • Save to file and load from file
    • You can save the output to a file at any time or load a file by dragging and dropping it into the input field. Files up to around 2GB are supported (depending on your browser), however, some operations may take a very long time to run over this much data.
  • CyberChef is entirely client-side
    • It should be noted that none of your recipe configuration or input (either text or files) is ever sent to the CyberChef web server - all processing is carried out within your browser, on your own computer.
    • Due to this feature, CyberChef can be downloaded and run locally. You can use the link in the top left corner of the app to download a full copy of CyberChef and drop it into a virtual machine, share it with other people, or host it in a closed network.

Deep linking

By manipulating CyberChef's URL hash, you can change the initial settings with which the page opens. The format is https://gchq.github.io/CyberChef/#recipe=Operation()&input=...

Supported arguments are recipe, input (encoded in Base64), and theme.

Browser support

CyberChef is built to support

  • Google Chrome 50+
  • Mozilla Firefox 38+

Node.js support

CyberChef is built to fully support Node.js v16. For more information, see the "Node API" wiki page

Contributing

Contributing a new operation to CyberChef is super easy! The quickstart script will walk you through the process. If you can write basic JavaScript, you can write a CyberChef operation.

An installation walkthrough, how-to guides for adding new operations and themes, descriptions of the repository structure, available data types and coding conventions can all be found in the "Contributing" wiki page.

  • Push your changes to your fork.
  • Submit a pull request. If you are doing this for the first time, you will be prompted to sign the GCHQ Contributor Licence Agreement via the CLA assistant on the pull request. This will also ask whether you are happy for GCHQ to contact you about a token of thanks for your contribution, or about job opportunities at GCHQ.

Licencing

CyberChef is released under the Apache 2.0 Licence and is covered by Crown Copyright.