Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
This is an OmniAuth strategy for authenticating to SignalWire.
gem 'omniauth-signalwire', '~> 0.1'
use OmniAuth::Builder do
provider :signalwire, ENV['SIGNALWIRE_KEY'], ENV['SIGNALWIRE_SECRET']
end
In config/initializers/signalwire.rb
Rails.application.config.middleware.use OmniAuth::Builder do
provider :signalwire, ENV['SIGNALWIRE_KEY'], ENV['SIGNALWIRE_SECRET']
end
An example auth hash available in request.env['omniauth.auth']
:
{
:provider => "signalwire",
:uid => "4d1bcf6e-88ed-4cfa-87bb-b986cd65678e",
:info => {
:email => "user@example.com",
:first_name => "Jane",
:last_name => "Doe",
:display_name => "Jane Doe",
...
},
:credentials => {
:token => "a1b2c3d4...", # The OAuth 2.0 access token
:refresh_token => "2QY...",
:expires_at => 1709194759,
:expires => true
},
:extra = {
:raw_info => {
...
}
}
}
Bug reports and pull requests are welcome on GitHub at https://github.com/ryanwi/omniauth-signalwire.
FAQs
Unknown package
We found that omniauth-signalwire demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers 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.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.