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.
This package provides a library whose purpose is to be a standard and universal configuration file manager for Node.js applications. Its main features are:
Because Slune is French firm, you will find all documents and messages in French. Other translations are welcome.
Anyway, because English is the language of programming, the code, including variable names and comments, are in English.
:fr: Une version française de ce document se trouve ici.
Installation is done using npm install
command:
$ npm install --save confinode
If you prefer using yarn
:
$ yarn add confinode
Choose your manual:
Even though we cannot guarantee a response time, please feel free to file an issue if you have any question or problem using the package. Pull Requests are also welcome.
FAQs
Node application configuration reader
The npm package confinode receives a total of 11,026 weekly downloads. As such, confinode popularity was classified as popular.
We found that confinode 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.