
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
A load balancer
$ npm i scale -g
$ scale -h
Usage: scale [options] [command]
Commands:
config show config
start start scale
stop stop scale
restart restart scale
* unknown command
Options:
-h, --help output usage information
-V, --version output the version number
-e, --edit edit config
$ scale start
info: starting scale on port 4141
$ scale config # show config
$ scale -e config # edit config
# Root directory to store scale data
root: $HOME/.scale
# Port on which scale runs
port: 1431
# List of servers to balance load
servers:
- name:
protocol: # http/https
hostname:
port:
# Routing technique
technique: # random/roundrobin
# Port forwarding
forward:
- port:
target:
hostname:
port:
Example npm/lib/node_modules/scale/config.yml
servers:
- name: s1
protocol: http
hostname: httpbin.org
- name: s2
protocol: http
hostname: stackoverflow.com
- name: s3
protocol: http
hostname: www.yahoo.com
technique: random
forward:
- port: 4545
target:
hostname: localhost
port: 22
FAQs
A load balancer
We found that scale 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
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.