cli
packj
cli | packj | |
---|---|---|
12 | 38 | |
99 | 615 | |
- | 3.3% | |
9.2 | 7.2 | |
about 7 hours ago | about 1 month ago | |
Rust | Python | |
GNU General Public License v3.0 only | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cli
-
Ledger's NPM account has been hacked
Co-funder @ Phylum here (https://phylum.io) We have been actively scanning dependencies across npm (and PyPI, RubyGems, Crates.io, etc.) for nearly three years now; quite successfully, I might add (https://blog.phylum.io/tag/research/). We _automatically_ hit on this package when it was published, and our research team has been all over it.
A collective of us are active in Discord (https://discord.gg/Fe6pr5eW6p), continuing to hunt attacks like these. If that's something that interests you, we'd love to have you!
In addition to this, we've released several open source tools to help protect against supply chain attacks:
1. https://github.com/phylum-dev/birdcage - Birdcage is a cross-platform embeddable sandbox that's been baked into our CLI (which wraps npm, pypi, etc.) to sandbox package installations
2. https://github.com/phylum-dev/cli - Our CLI provides an extension capability so you can lock down random executables you might use during your software development (define _what_ it's allowed to do, e.g. network access, and then lock it down with Birdcage)
We also have a variety of integrations, including Github, Gitlab, BitBucket, CircleCI, Tines, Sophos, etc.
https://docs.phylum.io/docs/integrations_overview
It's unfortunate that software dependency attacks continue to plague open source registries. It seems unlikely this will let up in the near future. We are continuing to work closely with the open source ecosystems to try and get these sorts of packages removed when they pop up.
- A Study of Malicious Code in PyPI Ecosystem
-
Rust Malware Staged on Crates.io
We're actively working on this with our sandbox (https://github.com/phylum-dev/birdcage). We've wrapped the likes of pip, yarn, and npm already and are making moves to similarly provide support for cargo.
Currently comes as part of the Phylum CLI (https://github.com/phylum-dev/cli), so that doing something like:
phylum npm install
-
How Attackers Can Sneakily Slip Malware Packages Into Poetry.lock Files
cli - uses sandbox to block packages during installation, performs pre-install checks to determine (by hitting the API) if the package performs actions congruent with malware, e.g. phylum pip install requests will use pip wrapped by the sandbox to install requests after verifying that it doesn't have malware like behavior.
-
Attackers Repurposing existing Python-based Malware for Distribution on NPM
This is bundled with our CLI tool today (which is also open source) and allows you to install packages with phylum npm install . We currently support npm, yarn and pip and are planning on rolling out further support for other ecosystems in coming months.
-
Attackers are hiding malware in minified packages distributed to NPM
We open sourced our tooling to help with this problem specifically. We have an extension framework that wraps npm for three purposes:
-
Active Malware Campaign Targeting Popular Python Packages Underway
Our CLI tool (also open source and free) will check for typosquats, dependency confusion, malicious code, vulnerabilities, etc. in your package dependencies. Works for pypi, npm, rubygems, maven, nuget and very recently golang and rust crates.
-
Ransomware being published to PyPI in ongoing campaign
This is built into the Phylum CLI so you can do things like:
-
Dozens of malicious PyPI packages discovered targeting developers
This is one of the projects we're working on (and open sourcing)!
Currently allows you to specify allowed resources during the package installation in a way very similar to what you've outlined [1].
The sandbox itself lives here [2] and can be integrated into other projects.
1. https://github.com/phylum-dev/cli/blob/main/extensions/npm/P...
2. https://github.com/phylum-dev/birdcage
-
How To: Open Source Policy Automation via Phylum Extensions
We will start here with a slightly more in-depth, custom version of the existing NPM shim extension - a tool that enforces default project policy when installing NPM packages. This custom extension will do some additional custom validation before allowing the installation process to continue.
packj
-
Rust Without Crates.io
Creator of Packj [1] here. How do you envision sandboxing/security policies will be specified? Per-lib policies when you've hundreds of dependencies will become overwhelming. Having built an eBPF-based sandbox [2], I anticipate that accuracy will be another challenge here: too restrictive will block functionality, too permissive defeats the purpose.
1. https://github.com/ossillate-inc/packj flags malicious/risky NPM/PyPI/RubyGems/Rust/Maven/PHP packages by carrying out static+dynamic+metadata analysis.
-
A Study of Malicious Code in PyPI Ecosystem
Cool project. How do you feel about projects like OpenSSF scorecards or even the checks that socket.dev do today on these packages to help determine risk?
https://github.com/ossillate-inc/packj/blob/main/.packj.yaml
Secondly, what about impersonation where attackers imitate a popular package and its respective metadata?
-
How to use Podman inside of a container
I built Packj [1] sandboxing for securing “pip/NPM install”. It uses strace for sandboxing and blocks access to sensitive files and limits traffic to known-good IP addresses.
1. https://github.com/ossillate-inc/packj
-
NPM Provenance Public Beta
Great work! This provenance check is going to be very valuable for enforcing supply-chain security. We are working on adding support to check for provenance in Packj.
1. https://github.com/ossillate-inc/packj flags risky/malicious NPM/PyPI/Ruby dependencies
-
Show HN: TypeScript Security Scanner
Cool project. Would love to integrate this in Packj [1] as one of the open-source SAST scanners. Will DM you.
1. https://github.com/ossillate-inc/packj flags malicious/risky open-source dependencies.
- Packj flags malicious/risky open-source packages
-
Show HN: Coder Guard – Protect Your IDE from Malicious Extensions
Very cool! I've built something similar, but for packages: https://github.com/ossillate-inc/packj Would love to talk.
-
Ask HN: What Are You Working on This Year?
Working on a marketplace (based on Packj [1]) to allow open-source developers to make money by selling "assured" software artifacts.
1. Packj https://github.com/ossillate-inc/packj flags malicious and other "risky" open-source dependencies in your software supply chain.
-
Compromised PyTorch-nightly dependency chain December 30th, 2022
I’ve created Packj sandbox [1] for “safe installation” of PyPI/NPM/Rubygems packages
1. https://github.com/ossillate-inc/packj
It DOES NOT require a VM/Container; uses strace. It shows you a preview of file system changes that installation will make and can also block arbitrary network communication during installation (uses an allow-list).
-
Vulnerability scanner written in Go that uses osv.dev data
Great to see a developer-friendly tool around OSV! Packj [1] uses OSV APIs to report vulnerable PyPI/NPM/Rubygems packages. Disclaimer: I built it.
1. https://github.com/ossillate-inc/packj flags malicious/risky packages.
What are some alternatives?
secimport - eBPF Python runtime sandbox with seccomp (Blocks RCE).
kubesploit - Kubesploit is a cross-platform post-exploitation HTTP/2 Command & Control server and agent written in Golang, focused on containerized environments.
steal-ur-stuff - Steal Ur Stuff
paperclips - Universal Paperclips mirror
rebuilderd - Independent verification of binary packages - reproducible builds
meta - Meta discussions and unicorns. Not necessarily in that order.
notes - Notes, Questions, Ideas
maloss - Towards Measuring Supply Chain Attacks on Package Managers for Interpreted Languages
pypi-scan - Scan pypi for typosquatting
roqr - QR codes that will rock your world
LavaMoat - tools for sandboxing your dependency graph
firejail - Linux namespaces and seccomp-bpf sandbox