App Crashed on heroku/vps

Error is posted

internal/buffer.js:77
  throw new ERR_OUT_OF_RANGE(type || 'offset',
  ^

RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 6. Received 8
    at boundsError (internal/buffer.js:77:9)
    at Buffer.readInt32BE (internal/buffer.js:473:5)
    at Object.exports.prepareKey (/usr/lib/node_modules/torrent-cloud/node_modules/mega/lib/crypto/index.js:35:24)
    at new Storage (/usr/lib/node_modules/torrent-cloud/node_modules/mega/lib/storage.js:75:21)
    at mega (/usr/lib/node_modules/torrent-cloud/node_modules/mega/lib/mega.js:9:10)
    at Object.exports.init (/usr/lib/node_modules/torrent-cloud/lib/backends/mega.js:12:13)
    at /usr/lib/node_modules/torrent-cloud/lib/backend.js:51:10
    at Array.forEach (<anonymous>)
    at Object.<anonymous> (/usr/lib/node_modules/torrent-cloud/lib/backend.js:21:10)
    at Module._compile (internal/modules/cjs/loader.js:1123:30) {
  code: 'ERR_OUT_OF_RANGE'
}

Start by tracing the reported stack from lib/backends/mega.js through lib/backend.js into the mega dependency's prepareKey and Storage calls. Determine what input causes the out-of-range offset when the application starts on Heroku or a VPS. Done means the application initializes the Mega backend without this RangeError, with a regression check for the reported startup path.