Comment by revicon

It's definitely using AWS Lamba, I spun up a trial account and texted myself the output of JSON.stringify(process.env)...

Edit: adding linebreaks...

2nd edit: Realized there were AWS access tokens in there. It's probably not a good idea for those to be exposed to the environment they're running this user generated code in. They should probably be wrapping these in vm.runInNewContext()

  {
  "PATH":"/var/lang/bin:/usr/local/bin:/usr/bin/:/bin",
  "LANG":"en_US.UTF-8",
  "TZ":":/etc/localtime",
  "LD_LIBRARY_PATH":"/var/lang/lib:/lib64:/usr/lib64:/var/runtime:/var/runtime/lib:/var/task:/var/task/lib",
  "LAMBDA_TASK_ROOT":"/var/task",
  "LAMBDA_RUNTIME_DIR":"/var/runtime",
  "AWS_REGION":"us-east-1",
  "AWS_DEFAULT_REGION":"us-east-1",
  "AWS_LAMBDA_LOG_GROUP_NAME":"/aws/lambda/ZDfb2ab7cd7ac1734d9a1a06a018a1c522",
  "AWS_LAMBDA_LOG_STREAM_NAME":"2017/05/25/[$LATEST]2d7b70d5a6914e3980f081ba96c9d4ab",
  "AWS_LAMBDA_FUNCTION_NAME":"ZDfb2ab7cd7ac1734d9a1a06a018a1c522",
  "AWS_LAMBDA_FUNCTION_MEMORY_SIZE":"512",
  "AWS_LAMBDA_FUNCTION_VERSION":"$LATEST", 
  "_AWS_XRAY_DAEMON_ADDRESS":"169.254.79.2",
  "_AWS_XRAY_DAEMON_PORT":"2000",
  "AWS_XRAY_DAEMON_ADDRESS":"169.254.79.2:2000",
  "AWS_XRAY_CONTEXT_MISSING":"LOG_ERROR",
  "_X_AMZN_TRACE_ID":"Root=1-59274f44-71756c3273bfaf4895cd5610;Parent=4126596e259f5d9f;Sampled=0",
  "AWS_EXECUTION_ENV":"AWS_Lambda_nodejs6.10",
  "_HANDLER":"enigma.handler",
  "NODE_PATH":"/var/runtime:/var/task:/var/runtime/node_modules",
  "AWS_ACCESS_KEY_ID":"REMOVINGTHIS",
  "AWS_SECRET_ACCESS_KEY":"ALSOREMOVINGTHIS",
  "AWS_SESSION_TOKEN":"REMOVINGTHISTOO"
  }