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 CLI is extensible and allows you to interact with online banking sites in general. Check below for implemented services and examples.
Google Chrome 59 is needed to use headless mode. You can also download Chrome Canary and use it alongside your current Chrome stable version.
A global installation is preferred:
npm i -g
Now exec ebank --help
for details on supported commands.
Create a .env
file in the root folder (with proper permissions!) with the specific vars required for authentication. For example: ebank bbva
would need the following vars:
BBVA_DNI=
BBVA_USER=
BBVA_PASSWORD=
Add specific credentials as needed by other commands.
You are welcome to submit a new online banking command utility :)
See API docs: https://chromedevtools.github.io/devtools-protocol/
FAQs
Extensible online banking command line interface
The npm package ebank-cli receives a total of 2 weekly downloads. As such, ebank-cli popularity was classified as not popular.
We found that ebank-cli 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.