
Research
Malicious npm Packages Impersonate Flashbots SDKs, Targeting Ethereum Wallet Credentials
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
winston-beanstalkd
Advanced tools
A Beanstalkd transport for winston.
To enable a log-based work queue compatible with existing logging mechanisms.
var winston = require('winston');
//
// Requiring `winston-beanstalkd` will expose
// `winston.transports.Beanstalkd`
//
require('winston-beanstalkd').Beanstalkd;
winston.add(winston.transports.Beanstalkd, options);
The Beanstalkd transport takes the following options. 'host' is required:
$ curl http://npmjs.org/install.sh | sh
$ npm install winston
$ npm install winston-beanstalkd
See the examples for a logger and a watcher.
In one console, start the watcher:
$ node examples/watch.js
Watching for logs on winston.log...
In another console, run the logger:
$ node examples/logger.js
info: Beanstalkd log event!
warn: This is a warning!
error: This is an error! code=505, anything=This is metadata
help: Log number 0
help: Log number 1
help: Log number 2
help: Log number 3
help: Log number 4
log put to winston.log { level: 'info',
text: ' Beanstalkd log event!',
meta: undefined }
closing...
log put to winston.log { level: 'warn', text: ' This is a warning!', meta: undefined }
closing...
log put to winston.log { level: 'error',
text: ' This is an error!',
meta: { code: '505', anything: 'This is metadata' } }
closing...
log put to winston.log { level: 'help', text: ' Log number 0', meta: undefined }
closing...
log put to winston.log { level: 'help', text: ' Log number 1', meta: undefined }
closing...
log put to winston.log { level: 'help', text: ' Log number 2', meta: undefined }
closing...
log put to winston.log { level: 'help', text: ' Log number 3', meta: undefined }
closing...
log put to winston.log { level: 'help', text: ' Log number 4', meta: undefined }
closing...
Return to the watcher console and see the output from processing the log entries:
$ node examples/watch.js
Watching for logs on winston.log...
received log: { id: '198',
data: '{"level":"info","text":" Beanstalkd log event!"}' }
processing log entry...
processed: true { id: '198',
data: '{"level":"info","text":" Beanstalkd log event!"}' }
deleted { id: '198',
data: '{"level":"info","text":" Beanstalkd log event!"}' }
[ 'DELETED' ]
Watching for logs on winston.log...
received log: { id: '199',
data: '{"level":"warn","text":" This is a warning!"}' }
processing log entry...
processed: true { id: '199',
data: '{"level":"warn","text":" This is a warning!"}' }
deleted { id: '199',
data: '{"level":"warn","text":" This is a warning!"}' }
[ 'DELETED' ]
Watching for logs on winston.log...
received log: { id: '200',
data: '{"level":"error","text":" This is an error!","meta":{"code":"505","anything":"This is metadata"}}' }
processing log entry...
processed: true { id: '200',
data: '{"level":"error","text":" This is an error!","meta":{"code":"505","anything":"This is metadata"}}' }
deleted { id: '200',
data: '{"level":"error","text":" This is an error!","meta":{"code":"505","anything":"This is metadata"}}' }
[ 'DELETED' ]
Watching for logs on winston.log...
received log: { id: '201', data: '{"level":"help","text":" Log number 0"}' }
processing log entry...
processed: true { id: '201', data: '{"level":"help","text":" Log number 0"}' }
deleted { id: '201', data: '{"level":"help","text":" Log number 0"}' }
[ 'DELETED' ]
Watching for logs on winston.log...
received log: { id: '202', data: '{"level":"help","text":" Log number 1"}' }
processing log entry...
processed: true { id: '202', data: '{"level":"help","text":" Log number 1"}' }
deleted { id: '202', data: '{"level":"help","text":" Log number 1"}' }
[ 'DELETED' ]
Watching for logs on winston.log...
received log: { id: '203', data: '{"level":"help","text":" Log number 2"}' }
processing log entry...
processed: true { id: '203', data: '{"level":"help","text":" Log number 2"}' }
deleted { id: '203', data: '{"level":"help","text":" Log number 2"}' }
[ 'DELETED' ]
Watching for logs on winston.log...
received log: { id: '204', data: '{"level":"help","text":" Log number 3"}' }
processing log entry...
processed: true { id: '204', data: '{"level":"help","text":" Log number 3"}' }
deleted { id: '204', data: '{"level":"help","text":" Log number 3"}' }
[ 'DELETED' ]
Watching for logs on winston.log...
received log: { id: '205', data: '{"level":"help","text":" Log number 4"}' }
processing log entry...
processed: true { id: '205', data: '{"level":"help","text":" Log number 4"}' }
deleted { id: '205', data: '{"level":"help","text":" Log number 4"}' }
[ 'DELETED' ]
Watching for logs on winston.log...
process callback
process callback
process callback
process callback
process callback
process callback
process callback
process callback
FAQs
An Beanstalkd transport for winston
The npm package winston-beanstalkd receives a total of 0 weekly downloads. As such, winston-beanstalkd popularity was classified as not popular.
We found that winston-beanstalkd 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.
Research
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
Security News
Ruby maintainers from Bundler and rbenv teams are building rv to bring Python uv's speed and unified tooling approach to Ruby development.
Security News
Following last week’s supply chain attack, Nx published findings on the GitHub Actions exploit and moved npm publishing to Trusted Publishers.