vouch
birdcage
vouch | birdcage | |
---|---|---|
10 | 13 | |
17 | 172 | |
- | 0.6% | |
0.0 | 7.3 | |
over 2 years ago | 18 days ago | |
Rust | Rust | |
MIT License | GNU General Public License v3.0 only |
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.
vouch
-
NPM repository flooded with 15,000 phishing packages
If you don't know the author, signatures do nothing. Anybody can sign their package with some key. Even if you could check the author's identity, that still does very little for you, unless you know them personally.
It makes a lot more sense to use cryptography to verify that releases are not malicious directly. Tools like crev [1], vouch [2], and cargo-vet [3] allow you to trust your colleagues or specific people to review packages before you install them. That way you don't have to trust their authors or package repositories at all.
That seems like a much more viable path forward than expecting package repositories to audit packages or trying to assign trust onto random developers.
[1]: https://github.com/crev-dev/crev [2]: https://github.com/vouch-dev/vouch [3]: https://github.com/mozilla/cargo-vet
- Dozens of malicious PyPI packages discovered targeting developers
-
Vetting the Cargo
Alternatives to cargo-vet that has been mentioned before here on HN:
- https://github.com/crev-dev/crev
- https://github.com/vouch-dev/vouch
Anyone know of any more alternatives or similar tools already available?
- Vouch – A multi-ecosystem package code review system
- Gitsign
-
Embedded malware in RC (NPM package)
I've created Vouch in an attempt to address this problem:
https://github.com/vouch-dev/vouch
Vouch lets users create and share reviews for NPM packages. Project dependencies can then be checked against those reviews.
Vouch uses extensions to interface with package ecosystems. It's simple to create a new extension. Extensions currently exist for NPM, PyPi, and Ansible Galaxy.
I'm currently working on a website to index known reviews and publish official reviews.
I hope you guys find it useful! Drop by the Matrix channel if you have any feedback to share: #vouch:matrix.org
- Vouch: A dependency review tool for NPM packages
- BREAKING!! NPM package ‘ua-parser-js’ with more than 7M weekly download is compromised
- Vouch: A dependency review tool for PyPI packages
birdcage
-
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.
-
Cryptocurrency Miner Masquerading as GCC Compiler Found in NPM Package
To be clear, this particular package did not execute code during install, so the sandbox wouldn't have come into play, but it would have been blocked by the pre-check against Phylum's API.
Would greatly appreciate any feedback on our extensions and suggestions for improving our sandbox! We recently had a few individuals submit some great issues and suggestions, which we absolutely loved receiving.
Happy to answer any questions about software supply chain attacks or security in general!
1. https://blog.phylum.io/junes-sophisticated-npm-attack-attrib...
2. https://blog.phylum.io/rust-malware-staged-on-crates-io/
3. https://blog.phylum.io/npm-emails-validator-package-malware/
4. https://github.com/phylum-dev/cli
5. https://github.com/phylum-dev/birdcage
-
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
-
Social engineering campaign targeting tech employees spreads through NPM malware
We (https://phylum.io) actually open sourced our sandbox for this exact purpose.
https://github.com/phylum-dev/birdcage
It's baked into our CLI and supports limiting access to network, disk, etc. during package installation. For example, running something like
phylum npm install react
-
Attackers Repurposing existing Python-based Malware for Distribution on NPM
We've open sourced our sandbox, which limits access to network/disk/etc. during package installation. In this way, nasty install scripts won't have the opportunity to ship your credentials/SSH keys off to a remote sever.
-
Attackers are hiding malware in minified packages distributed to NPM
The sandbox is also open source and available for use by the community.
-
Active Malware Campaign Targeting Popular Python Packages Underway
In addition to this, taking precautions to not install unknown packages is probably also extremely prudent. Towards that end, we've open sourced a cross platform embeddable sandbox for package installations. Source is freely available on Github (https://github.com/phylum-dev/birdcage) and we've added it into our tooling so you can run pip install ... and it'll limit access to disk, network, etc. during package installation.
-
Supply Chain Attack Using PyPI Packages “Colorslib”, “Httpslib”, and “Libhttps”
Been working on this exact thing for nearly two years at https://www.phylum.io. We identified and reported about 1.2k packages in ecosystems like npm, pypi and others last year. GitHub app that checks your PRs for malware. We also built a free open source sandbox for package installations [1] so if malware does get executed it’s done in a locked down environment. Happy to chat further about this sort of thing, it’s something I’m wildly interested in!
[1] https://github.com/phylum-dev/birdcage
- Ransomware currently being published to PyPI in ongoing campaign
-
Ransomware Python Packages Currently Being Published to PyPI
(Disclaimer: I'm one of the co-founders at Phylum)
Our system has been alerting us to this actor's activities all morning (beginning sometime last night). They have been wildly active, and have continued to publish packages as we've worked to get them removed.
Interestingly, they have ported the Python bits to Javascript and have started publishing to NPM as well. Exact same TTP, crossing two ecosystems.
Our platform monitors these ecosystems, scanning packages for signs of risk as they are published. This way we can get them removed before they impact the wider open source community. We currently support Javascript, Typescript, Python, Ruby, Java, C# and recently just rolled out Golang and Rust support into beta.
We believe in a defense in depth approach to supply chain security and have also published an open source sandbox that limits access to the filesystem, network, disk and environment variables.
https://github.com/phylum-dev/birdcage
This is rolled into our CLI so that you can do things like `phylum npm install ` and install packages in a sandboxed way.
Happy to answer questions about this attack, security, sandboxes, etc!
What are some alternatives?
npm-force-resolutions - Force npm to install a specific transitive dependency version
secimport - eBPF Python runtime sandbox with seccomp (Blocks RCE).
is-number - JavaScript/Node.js utility. Returns `true` if the value is a number or string number. Useful for checking regex match results, user input, parsed strings, etc.
packj - Packj stops :zap: Solarwinds-, ESLint-, and PyTorch-like attacks by flagging malicious/vulnerable open-source dependencies ("weak links") in your software supply-chain
gitsign - Keyless Git signing using Sigstore
conf - Simple config handling for your app or module
wapm-cli - 📦 WebAssembly Package Manager (CLI)
git-ts - Git TimeStamp Utility
lunasec - LunaSec - Dependency Security Scanner that automatically notifies you about vulnerabilities like Log4Shell or node-ipc in your Pull Requests and Builds. Protect yourself in 30 seconds with the LunaTrace GitHub App: https://github.com/marketplace/lunatrace-by-lunasec/
SES-shim - Endo is a distributed secure JavaScript sandbox, based on SES
Contents - Community documentation, code, links to third-party resources, ... See the issues and pull requests for pending content. Contributions are welcome !