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.
blinksocks
Advanced tools
A framework for building composable proxy protocol stack.
Looking for GUI? Here it is: https://github.com/blinksocks/blinksocks-gui
blinksocks is built on top of Node.js, if you want to use it in an ordinary way or do some hacking, please install Node.js(v8.x and above) on your operating system.
You can get the latest blinksocks via package manager yarn or npm.
NOTE: Node.js comes with npm installed so you don't have to install npm individually.
latest stable version
$ npm install -g blinksocks
nightly releases
Please check out blinksocks-nightly-releases.
$ blinksocks --help
For configuring blinksocks, please refer to Configuration.
See contributors.
Apache License 2.0
Migrating from 3.3.0 to 3.3.1
$ npm install -g blinksocks@3.3.1
FAQs
A framework for building composable proxy protocol stack
The npm package blinksocks receives a total of 20 weekly downloads. As such, blinksocks popularity was classified as not popular.
We found that blinksocks 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.