
Research
/Security News
Weaponizing Discord for Command and Control Across npm, PyPI, and RubyGems.org
Socket researchers uncover how threat actors weaponize Discord across the npm, PyPI, and RubyGems ecosystems to exfiltrate sensitive data.
google-authenticator-util
Advanced tools
Google authenticator tool for backend development / automation
This NodeJS module is built in order to make it easier to authenticate with google without knowing too much about how it works. This tool is recommended for both automation and development.
http://mydomain/oauth2callback
(Recommended is http://localhost:port/oauth2callback
) And type of Web application
Before starting, you need to initialize the constructor with the client and secret id's of oAuth2:
const authenticator = new GoogleAuthenticator({
clientId: 'your client ID',
clientSecret: 'your client secret'
});
In the first time, you don't have a token at all and you will to verify the auth URL using a browser. The following code will do it for you:
const oAuth2 = authenticator.authorizeWithNewToken({
scope: ['scope 1', 'scope 2'],
username: 'your email address username (before the @)',
password: 'your email address password'
});
After the first execution of the code, the token will be generated in tokens
folder by default and with a name of your-client-id-token.json
.
After the token is generated, it is recommended to remove the username and password parameters, they are no longer necessary.
After first token generation, you can re-use your token in the ways.
After first token was generated, you no longer need to pass the username and password parameters. Your code should look like:
const oAuth2 = authenticator.authorizeWithTokenFile({
name: 'my-token-file',
directory: './my-token-directory'
});
//Final token path would be: ./my-token-directory/my-token-file.json
If you don't want to store a token file, you can always re-use the existing token as a JS object inside the code:
const oAuth2 = authenticator.authorizeWithToken({
access_token: 'your access token',
refresh_token: 'your refresh token',
scope: ['scope 1', 'scope 2'],
token_type: 'the type of the token',
expiry_date: 1315241515
});
Now you can remove the generated token file and keep authenticating.
The strong point of this module, is it's pre-build easy to use oAuth2 client. To get a built oAuth2 Client without knowing too much, do the following in your code:
const authenticator = new GoogleAuthenticator({
clientId: 'your client ID',
clientSecret: 'your client secret'
});
//I'm using the authorizeWithNewToken function, but this can also done with the authorizeWithTokenFile and authorizeWithToken functions, explained above.
const oAuth2 = authenticator.authorizeWithNewToken({
scope: ['scope 1', 'scope 2'],
username: 'your email address username (before the @)',
password: 'your email address password'
});
Now the oAuth2 variable holds the oAuth2 object you need.
You can use the GMAIL Client used in the module, in order to perform your async actions:
const authenticator = new GoogleAuthenticator({
clientId: 'your client ID',
clientSecret: 'your client secret'
});
//I'm using the authorizeWithNewToken function, but this can also done with the authorizeWithTokenFile and authorizeWithToken functions, explained above.
const oAuth2 = authenticator.authorizeWithNewToken({
scope: ['scope 1', 'scope 2'],
username: 'your email address username (before the @)',
password: 'your email address password'
});
const messages = await authenticator.gmailAPI.users.messages.list({
userId: 'me',
labelIds: ['UNREAD'],
auth: oAuth2,
q: 'subject: my-email-title'
});
Or you can use the original gmail client:
const gmail = google.gmail('v1');
const messages = await gmail.users.messages.list({
userId: 'me',
labelIds: ['UNREAD'],
auth: oAuth2,
q: 'subject: my-email-title'
});
FAQs
Google authenticator tool for backend development / automation
The npm package google-authenticator-util receives a total of 29 weekly downloads. As such, google-authenticator-util popularity was classified as not popular.
We found that google-authenticator-util demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
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 how threat actors weaponize Discord across the npm, PyPI, and RubyGems ecosystems to exfiltrate sensitive data.
Security News
Socket now integrates with Bun 1.3’s Security Scanner API to block risky packages at install time and enforce your organization’s policies in local dev and CI.
Research
The Socket Threat Research Team is tracking weekly intrusions into the npm registry that follow a repeatable adversarial playbook used by North Korean state-sponsored actors.