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.
Client library for interaction with the rsbe API
This library allows one to interact with the R* Backend (rsbe) API.
RSBE_URL
RSBE_USER
RSBE_PASSWORD
e.g.,
export RSBE_URL='https://rsbe.example.com'
export RSBE_USER='foo'
export RSBE_PASSWORD='bar'
$ irb -I lib
irb> require 'rsbe/client'
=> true
irb> include Rsbe::Client
=> Object
irb> Partner.all.each {|p| puts p.id}
51213be7-c8de-4e06-8cc2-06bfc82cdd68
977e659b-886a-4626-8799-8979426ad2b3
...
...
irb> p = Rsbe::Client::Partner.all.first
=> #<Rsbe::Client::Partner:0x007fdc81b4ec08 ...>
irb> puts "#{p.id} : #{p.code} : #{p.name}"
51213be7-c8de-4e06-8cc2-06bfc82cdd68 : bar :
=> nil
irb> p.name = 'Foo Bar'
=> "Foo Bar"
irb> p.save
=> true
> p = Rsbe::Client::Partner.find('51213be7-c8de-4e06-8cc2-06bfc82cdd68')
=> #<Rsbe::Client::Partner:0x007fdc81a3cdd8 ...>
irb> puts "#{p.id} : #{p.code} : #{p.name}"
51213be7-c8de-4e06-8cc2-06bfc82cdd68 : bar : Foo Bar
=> nil
FAQs
Unknown package
We found that rsbe-client 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.
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.