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.
Chief is an Application Container for use with Amazon Web Service Auto-Scaling Groups.
An application container provides the following:
Procfile
A auto-scaling groups are great. Chief helps make them even better.
npm install -g chief
sudo chief upstart -o /etc/init/chief.conf
/home/ubuntu/bundle/master
Chief reads the environment configuration from the AWS user-data property, and passes it to your application.
Chief can run any kind of application, not just Node.js.
Chief runs Procfile application; the root of your bundle must contain a Profile
like the following:
web: node server.js
log: node logger.js
Chief is designed to work in production. Each process in your Procfile is started independently, and will be restarted if it crashes.
/var/log/chief/<proc-key>.log
sudo start chief
sudo stop chief
web=2,log=1
FAQs
Polyglot Server Application Running
The npm package chief receives a total of 0 weekly downloads. As such, chief popularity was classified as not popular.
We found that chief 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.