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.
A stream pipeline based message processing framework.
npm install billow
'use strict'
const { Billow, Flow, Droplet } = require('billow')
let billow = new Billow({ separator: '\r\n' })
let flowOne = new Flow({ events: ['error', 'dropletError'] })
let flowTwo = new Flow({ events: ['error', 'dropletError'] })
flowOne.on('error', console.error).on('dropletError', console.error)
flowTwo.on('error', console.error).on('dropletError', console.error)
flowOne.addDroplets([
new Droplet({
handler: async function (chunk, encoding) {
return await Promise.resolve(`${chunk.toString()}==`)
}
}),
new Droplet({
handler: function (chunk, encoding) {
console.log(chunk.toString())
}
})
])
flowTwo.addDroplets([
new Droplet({
handler: async function (chunk, encoding) {
return await Promise.resolve(`${chunk.toString()}~~`)
}
}),
new Droplet({
handler: function (chunk, encoding) {
console.log(chunk.toString())
}
})
])
billow.addFlow(flowOne).addFlow(flowTwo).write('billow!\r\nbillow!\r\n')
// billow!==
// billow!~~
// billow!==
// billow!~~
Billow
's workflow is based on Flow
which is the combination of Droplet
s. Each Droplet
is an implementation of Node.js transform stream, in which you can use async / await
function to handle the asynchronous data processing logic with happiness. And Flow
is the abstact pipeline of those Droplet
s, so the data transmission in Flow
is very fast and heap memory saved. Because Node.js transform stream will buffer the data when there is no downstream, so all data in Flow
s will be piped to a writable stream which name is blackHole
eventually to prevent the potential resident memory leak.
| => flow one => |
| ( droplet(1) => droplet(2) => ... ) |
| |
data => | => flow two => | => blackHole
| ( droplet(4) => droplet(3) => ... ) |
| |
| => other flows => |
Number
: The separator to separate the in coming buffer, if separator is set to be null
, then billow
will pass the buffer directly to the flows
, by default it is '\r\n'
.Number
: If provided, it will be passed to the inside stream.Writable
contructor.return a new instance of Billow
.
Flow
: An instance of flow
.Register a new flow
to billow
.
Array<String>
: The events you want to listen emitted from the droplet
s of this flow
.return a new instance of Flow
.
Droplet | Array<Droplet>
: The droplet
s you want to add to the flow
.Register new droplets
to flow
.
async function (chunk, encoding) {}
: The handler to process the chunk
, the value this function returns will be pass to the next droplet
in current flow
.Number
: If provided, it will be passed to the inside stream.Transform
contructor.return a new instance of Droplet
.
FAQs
A stream pipeline based message processing framework
We found that billow 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.