Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
github.com/m1guelpf/chatgpt-telegram
Interact with ChatGPT
Go CLI to fuels a Telegram bot that lets you interact with ChatGPT, a large language model trained by OpenAI.
Download the file corresponding to your OS in the releases page.
chatgpt-telegram-Darwin-amd64
: macOS (Intel)chatgpt-telegram-Darwin-arm64
: macOS (M1)chatgpt-telegram-Linux-amd64
: Linuxchatgpt-telegram-Linux-arm64
: Linux (ARM)chatgpt-telegram-Win-amd64
: WindowsAfter you download the file, extract it into a folder and open the env.example
file with a text editor and fill in your credentials.
TELEGRAM_TOKEN
: Your Telegram Bot token
TELEGRAM_ID
(Optional): Your Telegram User ID
@userinfobot
on Telegram.EDIT_WAIT_SECONDS
(Optional): Amount of seconds to wait between edits
1
by default, but you can increase if you start getting a lot of Too Many Requests
errors..env
.Note Make sure you rename the file to exactly
.env
! The program won't work otherwise.
Finally, open the terminal in your computer (if you're on windows, look for PowerShell
), navigate to the path you extracted the above file (you can use cd dirname
to navigate to a directory, ask ChatGPT if you need more assistance 😉) and run ./chatgpt-telegram
.
If you're trying to run this on a server with an existing Docker setup, you might want to use our Docker image instead.
docker pull ghcr.io/m1guelpf/chatgpt-telegram
Here's how you'd set things up with docker-compose
:
services:
chatgpt-telegram:
image: ghcr.io/m1guelpf/chatgpt-telegram
container_name: chatgpt-telegram
volumes:
# your ".config" local folder must include a "chatgpt.json" file
- .config/:/root/.config
environment:
- TELEGRAM_ID=
- TELEGRAM_TOKEN=
Note The docker setup is optimized for the Browserless authentication mechanism, described below. Make sure you update the
.config/chatgpt.json
file in this repo with your session token before running.
By default, the program will launch a browser for you to sign into your account, and close it once you're signed in. If this setup doesn't work for you (there are issues with the browser starting, you want to run this in a computer with no screen, etc.), you can manually extract your session from your browser instead.
To do this, first sign in to ChatGPT on your browser, then open the Developer Tools (right click anywhere in the page, then click "Inspect"), click on the Application tab and then on the Cookies section, and copy the value of the __Secure-next-auth.session-token
cookie.
You will then have to create a config file in the following location depending on your OS (replace YOUR_USERNAME_HERE
with your username:
~/.config/chatgpt.json
: LinuxC:\Users\YOUR_USERNAME_HERE\AppData\Roaming\chatgpt.json
: Windows/Users/YOUR_USERNAME_HERE/Library/Application Support/chatgpt.json
: macOSNote If you have already run the program, the file should exist but be empty. If it doesn't exist yet, you can either run the program or manually create it.
Finally, add your cookie to the file and save it. It should look like this: { "openaisession": "YOUR_COOKIE_HERE" }
.
This repository is licensed under the MIT License.
FAQs
Unknown package
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.