Research
Security News
Threat Actor Exposes Playbook for Exploiting npm to Build Blockchain-Powered Botnets
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.
Monitor one-off tasks on your servers using Redis.
npm install -g kwikemon
$ kwikemond &
$ curl -s localhost/nginx_status | grep Active | kwikemon write nginx-connections
$ curl localhost:1111/nignx-connections
Active connections: 316
$ kwikemon set foo bar
$ curl localhost:1111/
foo: bar
nginx-connections: Active connections: 316
Here's how it works:
kwikemon set thing status
to set the text for the monitor named "thing"kwikemond
, that serves up these monitors in a big list or individuallyAlternatively:
kwikemon write <name of thing you are watching>
on stdinTo see everything kwikemon
can do run kwikemon help
.
$ kwikemon help
This is very much a work in progress.
You can use kwikemon as a library.
var kwikemon = require('kiwkemon');
kwikemon.set('foo', 'bar', function(err) {
kwikemon.get('foo', function(err, text) {
console.log('foo = ' + text);
});
});
kwikemon.getAll(function(err, monitors) {
Object.keys(monitors).forEach(function (name) {
console.log(name + ' = ' + monitors[name]);
});
});
Monitors expire 1 day after the last time they were set by default. You can pass in any ttl
you
want though.
// never expire
kwikemon.set('foo', 'bar', { ttl: 0 });
All kwikemon does is shove things into Redis in a standard way and read them out later.
A monitor named nginx
stores its data in the hash kwikemon:monitor:nginx
. Hash fields
are:
The list of all monitors is a set stored at kwikemon:monitors
.
exists = redis.exists("kwikemon:monitor:nginx")
if exists:
redis.hmset("kwikemon:monitor:nginx", {
text: "Active connections: 583"
modified: 1370668341943
})
redis.hincrby("kwikemon:monitor:nginx", "updates", 1)
else:
redis.hmset("kwikemon:monitor:nginx", {
text: "Active connections: 316"
updates: 1
created: 1370668301943
modified: 1370668301943
})
redis.sadd("kwikemon:monitors", "nginx")
# optional
redis.expire("kwikemon:monitor:nginx", <ttl>)
redis.hgetall("kwikemon:monitor:nginx")
redis.del("kwikemon:monitor:nginx")
redis.srem("kwikemon:monitors", "nginx")
Clean out expired monitors. Call this before anything that relies on counting or iterating through all monitors.
for name in redis.smembers("kwikemon:monitors"):
if not redis.exists("kwikemon:monitor:$name"):
remove(name)
Sweep before running a count.
sweep()
redis.scard("kwikemon:monitors")
Sweep before listing.
sweep()
redis.smembers("kwikemon:monitors")
Sweep before geting all.
sweep()
monitors = {}
for name in list():
if redis.exists("kwikemon:monitor:$name"):
monitors[name] = get(name)
return monitors
Copyright 2013 Sami Samhuri sami@samhuri.net
FAQs
monitor one-off things on your servers
We found that kwikemon 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
Security News
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.
Security News
NVD’s backlog surpasses 20,000 CVEs as analysis slows and NIST announces new system updates to address ongoing delays.
Security News
Research
A malicious npm package disguised as a WhatsApp client is exploiting authentication flows with a remote kill switch to exfiltrate data and destroy files.