Decrypting Salted Base64 of using Google Apps Script


This sample script decrypts the salted base64 data of using Google Apps Script.

Recently, it seems that the specification of the key for decrypting the data has been changed at the server side. So. in this post, this post is updated. About this specification, I checked this thread.

Sample script

function myFunction() {
  // Load crypto-js.min.js.
  const cdnjs =

  // Retrieve HTML and retrieve salted base64.
  const url = ""; // This is a sample URL.
  const html = UrlFetchApp.fetch(url)
    .match(/root.App.main = ([\s\S\w]+?);\n/);
  if (!html || html.length == 1) return;
  const tempObj = JSON.parse(html[1].trim());
  let obj;
  if (
    typeof tempObj.context.dispatcher.stores === "string" ||
    tempObj.context.dispatcher.stores instanceof String
  ) {
    // Decrypt the salted base64.
    var key = Object.entries(tempObj).find(
      ([k]) => !["context", "plugins"].includes(k)
    if (!key) {
      throw new Error(
        "Specification at the server side might be changed. Please check it."
    obj = JSON.parse(
        CryptoJS.AES.decrypt(tempObj.context.dispatcher.stores, key)
  } else {
    obj = tempObj.context.dispatcher.stores;
  • About the value of context.dispatcher.stores, this script can be used for both the salted base64 and the JSON object.


  • In this sample, in order to load crypto-js, eval(UrlFetchApp.fetch(cdnjs).getContentText()) is used. But, if you don’t want to use it, you can also use this script by copying and pasting the script of to the script editor of Google Apps Script. By this, the process cost can be reduced.


  • I can confirm that this method can be used for the current situation (January 14, 2023). But, when the specification in the data and HTML is changed in the future update on the server side, this script might not be able to be used. Please be careful about this.