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 Harvesting credit card numbers and passwords from your site (2018)
I've been building Packj [1] to address exactly these types of supply chain attacks. It can audit PyPI/NPM/Rubygems packages and flag hidden malware or "risky” code behavior such as spawning of shell, exfiltration of data, mismatching repo code vs packaged code (provenance).

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

ashishbijlani··on Show HN: Coder Guard – Protect Your IDE from Malicious Extensions
Great! Let’s connect. Email in my profile.
ashishbijlani··on 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.
ashishbijlani··on Supply Chain Attack Using PyPI Packages “Colorslib”, “Httpslib”, and “Libhttps”
This. Moreover, such typo-squatting attacks could easily be mitigated by using a private package registry.
ashishbijlani··on Supply Chain Attack Using PyPI Packages “Colorslib”, “Httpslib”, and “Libhttps”
We’re building a private registry based on Packj [1] that hosts vetted artifacts. Will post more about it publicly soon.

1. https://github.com/ossillate-inc/packj flags malicious/risky packages.

ashishbijlani··on Supply Chain Attack Using PyPI Packages “Colorslib”, “Httpslib”, and “Libhttps”
I've been building Packj [1] to address exactly this problem. You can _audit_ as well as _sandbox_ installation of PyPI/NPM/Rubygems packages and flags hidden malware or "risky” code behavior such as spawning of shell, use of SSH keys, and mismatch of GitHub code vs packaged code (provenance).

1. https://github.com/ossillate-inc/packj flags malicious/risky packages.

ashishbijlani··on Compromised PyTorch-nightly dependency chain between December 25th – December 30
Thanks for highlighting this! While PTRACE introduces TOCTTOU vulnerabilities, Packj sandboxes fixes that by using read-only args for ptrace. You can find my PhD work [1] on this relevant.

1. https://lwn.net/Articles/803890/

ashishbijlani··on Compromised PyTorch-nightly dependency chain between December 25th – December 30
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).

ashishbijlani··on Compromised PyTorch-nightly dependency chain between December 25th – December 30
I started with static/dynamic analysis in Packj [1] to vet PyPI/NPM/Rubygems packages and flags hidden malware or "risky” code behavior such as spawning of shell, use of SSH keys, and mismatch of GitHub code vs packaged code (provenance).

1. https://github.com/ossillate-inc/packj flags malicious/risky packages.

ashishbijlani··on Compromised PyTorch-nightly dependency chain between December 25th – December 30
Plug: I've been building Packj [1] to address exactly this problem. You can _audit_ as well as _sandbox_ installation of PyPI/NPM/Rubygems packages and flags hidden malware or "risky” code behavior such as spawning of shell, use of SSH keys, and mismatch of GitHub code vs packaged code (provenance).

1. https://github.com/ossillate-inc/packj flags malicious/risky packages.

ashishbijlani··on Python malware starting to employ anti-debug techniques
I’ve been building Packj [1] to flag PyPI/NPM/Ruby packages that contain suspicious decode+exec and other “risky” APIs using static analysis. It also uses strace-based dynamic analysis to monitor install-time filesystem/network activities. We have detected a bunch of malware with the tool.

1. https://github.com/ossillate-inc/packj flags malicious/risky packages.

ashishbijlani··on Vulnerability scanner written in Go that uses osv.dev data
We've an open-source project that does this: https://github.com/osssanitizer/maloss I'm working on creating a CLI/web interface for this. Happy to chat (email in profile).
ashishbijlani··on 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.

ashishbijlani··on Show HN: Panoptisch – A recursive dependency scanner for Python projects
Good to see this project here! Have you added support for permissions already? Would love to integrate this in https://github.com/ossillate-inc/packj
ashishbijlani··on Ransomware Python Packages Currently Being Published to PyPI
Plug: I've been building Packj [1] to address exactly this problem. It offers “audit” as well as “sandboxing” of PyPI/NPM/Rubygems packages and flags hidden malware or "risky” code behavior such as spawning of shell, use of SSH keys, and mismatch of GitHub code vs packaged code (provenance).

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

ashishbijlani··on Ask HN: What Are You Working On? (December 2022)
I'm building Packj [1] to flag malicious/risky open-source dependencies. It offers “audit” as well as “sandboxing” of PyPI/NPM/Rubygems packages and reports hidden malware or "risky” code behavior such as spawning of shell, use of SSH keys, and mismatch of GitHub code vs packaged code (provenance). Found a bunch of malicious packages on PyPI/RubyGems using the tool, which have now been taken down.

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

ashishbijlani··on Analysis on Docker Hub malicious images: Attacks through public container images
While no automated tool can accurately catch all malware, I'm building Packj [1] to provide objective security insights into software artifacts. Auditing hundreds of direct/transitive dependencies manually is impractical, but Packj can quickly point out spawning of shell, use of SSH keys, mismatch of GitHub code vs packaged code (provenance), etc.

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

ashishbijlani··on Ask HN: What is the most impactful thing you've built?
I'm building Packj [1] to flag malicious/risky open-source dependencies. It offers “audit” as well as “sandboxing” of PyPI/NPM/Rubygems packages and reports hidden malware or "risky” code behavior such as spawning of shell, use of SSH keys, and mismatch of GitHub code vs packaged code (provenance). We found a bunch of malicious packages on PyPI/RubyGems using the tool, which have now been taken down.

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

ashishbijlani··on Show HN: I built VS Code extension for Node.js package management
I like how it enables package search right in IDE. I'd be interested to integrate Packj [1]. Sent you an email.

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

ashishbijlani··on Dozens of malicious PyPI packages discovered targeting developers
I built Packj to flag such "risky" packages: https://github.com/ossillate-inc/packj
ashishbijlani··on Ask HN: Ways to run container inside container for development purpose?
Take a look at Nestybox's DID use case [1]. They got acquired by Docker

1. https://blog.nestybox.com/2019/11/11/docker-sandbox.html

ashishbijlani··on Dozens of malicious PyPI packages discovered targeting developers
Are you suggesting that you would rather wait for languages to provide robust sandboxing capabilities and not use available static/dynamic analysis tools (e.g., Packj [1]) to audit packages for malicious/risky indicators, particularly when we hear about new attacks on open-source package managers almost every week?

1. https://github.com/ossillate-inc/packj [Disclaimer: I built it]

ashishbijlani··on Dozens of malicious PyPI packages discovered targeting developers
That’s exactly why I use strace-based to sandbox ALL dependencies: https://github.com/ossillate-inc/packj
ashishbijlani··on Dozens of malicious PyPI packages discovered targeting developers
This is exactly what Packj [1] scans packages for (30+ such risky attributes). Many packages will use base64 for benign reasons, this is why no fully-automated tool could be 100% accurate.

Manual auditing 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. Alerts could be commented out if don't apply.

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

Disclaimer: I developed this.

ashishbijlani··on Dozens of malicious PyPI packages discovered targeting developers
Plug: I've been building Packj [1] to address exactly this problem. It offers “audit” as well as “sandboxing” of PyPI/NPM/Rubygems packages and flags hidden malware or "risky” code behavior such as spawning of shell, use of SSH keys, and mismatch of GitHub code vs packaged code (provenance).

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

ashishbijlani··on Dozens of malicious PyPI packages discovered targeting developers
Packj sandbox [1] offers "safe installation" of PyPI/NPM/Rubygems packages.

1. https://github.com/ossillate-inc/packj/blob/main/packj/sandb...

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).

Disclaimer: I've been building Packj for over a year now.

ashishbijlani··on Jetstack Paranoia: A New Open-Source Tool for Container Image Security
I built Packj https://github.com/ossillate-inc/packj to scan NPM/PyPI/Ruby packages for CVEs and malicious/risky attributes.
ashishbijlani··on “You meant to install ripgrep”
Tools like Packj[1] that check for typosquatting and install packages under a sandbox can help in avoiding accidental installation of malicious packages. Disclaimer: I’m one of the devs.

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

ashishbijlani··on PyPI package 'secretslib' drops fileless Linux malware to mine Monero
Thanks! Would love to receive code contributions from rare folks like you who have binary analysis expertise. Currently, it uses strace to track process/net/fs system calls on Linux.
ashishbijlani··on PyPI package 'secretslib' drops fileless Linux malware to mine Monero
Packj https://github.com/ossillate-inc/packj can easily detect such malicious packages by pointing out if a package accesses sensitive files (e.g., SSH keys), spawns executables, exfiltrates data, is abandoned, lacks 2FA, etc. Disclaimer: I built it.
← PreviousPage 3 of 4Next →