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.
barnacle-mode
Advanced tools
A shorthand for creating object mode streams. The intention is to have an object mode stream that receives an object, appends keys, and then pipes it on. Almost like middleware but streaming.
Install the module with: npm install barnacle-mode
Create a new stream with:
var helloWorld = barnacleMode(function (obj, done) {
obj.hello = 'world';
done(null, obj);
});
The returned function can be called to create new instances of this stream:
hw = helloWorld();
someOtherObjectStream.pipe(hw);
If you have a stream which you intend to output a buffer (ie. not object mode) on the readable side, pass true as the second parameter when calling barnacleMode:
var callback = function (obj, done) { done(null, obj); };
var outputsBuffer = barnacleMode(callback, true);
This will allow you to provide an object mode stream which eventually passes its data through to a standard stream.
FAQs
Build up an object with streams
We found that barnacle-mode 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.