HNHacker News
TopNewBestAskShowJobs

ashishbijlani

220 karma · joined July 8, 2015

PhD in Cybersecurity/Operating Systems from Georgia Tech

Building https://packj.dev - a security firewall for your open-source dependencies to protect against typo-squatting, dependency confusion, and Solarwinds-like supply-chain attacks: https://github.com/ossillate-inc/packj

Creator of ExtFUSE (eBPF + FUSE) and SandFS [available for consulting]: https://github.com/extfuse/extfuse https://github.com/sandfs/sandfs.github.io

https://twitter.com/ashishbijlani https://www.linkedin.com/in/ashishbijlani/

first.last@<popular-google-service.com>

submissionscomments
ashishbijlani··on No, you cannot trust third party code without reading it first
Plug: I've been building tooling to easily audit third-party open-source dependencies for supply chain attacks. Packj [1] analyzes Python/NPM/Rubygems packages for several risky code and attributes such as Network/File permissions, expired email domains, etc. Auditing hundreds of direct/transitive dependencies manually is impractical, but Packj can quickly point out if a package accesses sensitive files (e.g., SSH keys), spawns shell, exfiltrates data, is abandoned, lacks 2FA, etc. It can be customized to your threat model by commenting out alerts that don't apply. We found a bunch of malicious packages on PyPI using the tool, which have now been taken down; a few are listed here https://packj.dev/malware

1. https://github.com/ossillate-inc/packj

ashishbijlani··on PyPI: Python packets steal AWS keys from users
We've created a Github action [1]. It pulls data from our backend service https://packj.dev that continuously scans packages. You will have to create a free account.

1. https://github.com/marketplace/actions/packj-dev-audit

ashishbijlani··on PyPI: Python packets steal AWS keys from users
By pinning versions, running Packj on deps and manual analysis :)
ashishbijlani··on PyPI: Python packets steal AWS keys from users
Sure. Please email me (in profile) for the list. You can also look at the following resources for malware samples:

1. https://github.com/IQTLabs/software-supply-chain-compromises 2. https://github.com/rsc-dev/pypi_malware 3. https://github.com/osssanitizer/maloss/blob/master/malware/R...

ashishbijlani··on PyPI: Python packets steal AWS keys from users
Yes, we are incorporating strace-based dynamic analysis (containerized) to collect system calls. However, Packj can currently flag use of getattr() API as it is equivalent to "runtime code generation" [1]; a developer can go and take a deeper look then.

1. https://github.com/ossillate-inc/packj/blob/main/main.py#L47...

ashishbijlani··on PyPI: Python packets steal AWS keys from users
Packj currently uses static code analysis to derive permissions (e.g., file/network accesses). Therefore, it can detect open() calls if used by the malware directly (e.g., not obfuscated in a base64 encoded string). But, Packj can also point out such base64 decode calls. Fortunately, malware has to use these APIs (read, open, decode, eval, etc.) for their functionality -- there's no getting around. Having said that, a sophisticated malware can hide itself better, so dynamic analysis as you suggested must be performed for completeness. We are incorporating strace-based dynamic analysis (containerized) to collect system calls.
ashishbijlani··on PyPI: Python packets steal AWS keys from users
> a base 64 encrypted string that gets decrypted and then passed to a shell.

This is a very common malicious behavior. Packj detects obfuscation [1] as well as spawning of shell commands (exec system call) [2]. I've updated threats.csv to flag code obfuscation.

1. https://github.com/ossillate-inc/packj/blob/main/main.py#L48... 2. https://github.com/ossillate-inc/packj/blob/main/main.py#L48...

ashishbijlani··on PyPI: Python packets steal AWS keys from users
Thanks for trying it out and sharing your feedback! I will fix this issue and also create a Dockerfile for easy testing.
ashishbijlani··on PyPI: Python packets steal AWS keys from users
I've been building tooling to mitigate supply chain attacks like these. Packj [1] analyzes Python/NPM packages for risky code and attributes such as Network/File permissions, expired email domains, etc. Auditing hundreds of direct/transitive dependencies manually is impractical, but Packj can quickly point out access to sensitive files (e.g., SSH keys), spawning shell, data exfiltration, etc. We found a bunch of malicious packages on PyPI using the tool, which have now been taken down; a few are listed here https://packj.dev/malware

1. https://github.com/ossillate-inc/packj

ashishbijlani··on Top-500 NPM package maintainers now require 2FA
Have they already enforced 2FA? The tool that I built to detect "risky" NPM/PyPI packages [1] still shows expired email domain for browserify (a top NPM package)

1. https://github.com/ossillate-inc/packj

ashishbijlani··on Show HN: Find NPM Package Alternatives
Would love to integrate this in https://github.com/ossillate-inc/packj
ashishbijlani··on Ask HN: What is the most interesting software you wrote in a few days?
I've been building tooling to mitigate open-source supply chain attacks. Packj [1] analyzes Python/NPM packages for risky code and attributes such as Network/File permissions, expired email domains, etc. Auditing hundreds of direct/transitive dependencies manually is impractical, but Packj can quickly point out "risky" attributes that must be checked. We found a bunch of malicious packages on PyPI using the tool, which have now been taken down; a few are listed here https://packj.dev/malware Would love to get your feedback.

1. https://github.com/ossillate-inc/packj

ashishbijlani··on Today’s JavaScript, from an outsider’s perspective (2020)
Packj tool (https://github.com/ossillate-inc/packj) analyzes Python/NPM packages for risky code and attributes such as Network/File permissions expired email domains. It uses static code analysis. We are adding support for Rust. We found a bunch of malicious packages on PyPI using the tool, which have now been taken down: examples https://packj.dev/malware [disclosure: I’m one of the developers]
ashishbijlani··on Python utility for tracking third party dependencies within a library
https://github.com/ossillate-inc/packj analyzes Python/NPM packages for risky code and metadata attributes. Uses static code analysis. We found a bunch of malicious packages on PyPI using the tool, which have now been taken down: examples https://packj.dev/malware [disclosure: I’m one of the developers]
ashishbijlani··on Execute Docker Containers as QEMU MicroVMs
fork here is COW on the host kernel (i.e., copying EPT entries). We will post detailed technical documentation soon.
ashishbijlani··on Execute Docker Containers as QEMU MicroVMs
No, gVisor is from Google. They emulate system calls in user-space and use VMs, which increases runtime performance overhead. We use hardware virtualization to directly run containers -- no I/O emulation, no expensive VM exits, scale as needed. Initial comparison with FC/GVisor/Xen here: https://github.com/ashishbijlani/kwarantine
ashishbijlani··on Execute Docker Containers as QEMU MicroVMs
> Can we somehow combine the advantages of the docker ecosystem with VMs?

Shameless plug: this is exactly what our goal is with https://kwarantine.xyz We are creating a new hypervisor (from scratch) that can run strongly isolated Docker/LXC containers.

ashishbijlani··on The Need for Slimmer Containers
We've been working on a new hypervisor https://kwarantine.xyz that can run strongly isolated containers. It’s still a WIP though.
ashishbijlani··on Hypervisor for multi-tenant computing, like it should be
Being security/systems researchers, that's exactly what our goals are as well.
ashishbijlani··on Hypervisor for multi-tenant computing, like it should be
Yes, we will post the numbers soon. However, what I was alluding to in my last comment was that FC runtime performance is far from native (i.e., no VMs). Therefore, there's definitely room for improvement. Depending on the use case, that may or may not be meaningful.
ashishbijlani··on Hypervisor for multi-tenant computing, like it should be
It depends on the requirements. We can start as early as next month. Would it be possible for you to get in touch on our Slack?
ashishbijlani··on Hypervisor for multi-tenant computing, like it should be
Thanks! We will post detailed technical docs on design/features soon. FC improved kernel boot up time (by stripping unnecessary functionality). However, runtime performance takes a hit due to I/O virtualization/emulation: https://www.usenix.org/system/files/nsdi20-paper-agache.pdf
ashishbijlani··on Hypervisor for multi-tenant computing, like it should be
Thanks for the feedback! We are still trying to figure out the business model.
ashishbijlani··on Hypervisor for multi-tenant computing, like it should be
There was a question (now deleted) on difference between this and Firecracker. FC/gVisor/Kata use VMs to sandbox containers. However, VMs incur high runtime overhead (not to be confused with fast booting) and need to be provisioned. We use hardware virtualization to directly run system/app containers -- no I/O emulation, no expensive VM exits, scale as needed.
ashishbijlani··on Hypervisor for multi-tenant computing, like it should be
Hello HN! We've been working on a new hypervisor https://kwarantine.xyz that can run strongly isolated containers. This is still a WIP, but we wanted to give the community an idea about our approach, its benefits, and various use cases it unlocks. Today, VMs are used to host containers, and make up for the lack of strong security as well as kernel isolation in containers. This work adds this missing security piece in containers. We plan on launching a free private beta soon. Meanwhile, we'd deeply appreciate any feedback, and happy to answer any questions here or on our slack channel. Thanks!
ashishbijlani··on Ask HN: How many projects do you work on at a time?
I prefer to focus on one at a time. My current project is a hypervisor that runs containers: https://kwarantine.xyz
ashishbijlani··on Show HN: Launch VM workloads securely and instantaneously, without VMs
Xen is a full-fledged hypervisor that hosts VMs. It uses QEMU for I/O emulation in VMs, which increases the attack surface.

Kwarantine is a thin hypervisor that hosts containers. It uses hardware virtualization extensions, MMU, and page tables to provide the same level of security as VMs. Each container runs with a separate copy of the host kernel so that vulnerabilities/bugs are isolated. It does not use QEMU.

ashishbijlani··on Show HN: Launch VM workloads securely and instantaneously, without VMs
I believe they are constantly working on optimizing their infrastructure, and we will see improved versions of gVisor and Firecracker soon.
ashishbijlani··on Show HN: Launch VM workloads securely and instantaneously, without VMs
Posting direct link here for convenience: https://kwarantine.xyz
ashishbijlani··on FUSE performance improvements with eBPF [pdf]
Author here. I’ve implemented this already and the kernel changes are available on GitHub. Please read section 5.2 in the Usenix paper for details.
← PreviousPage 4 of 4