Re:A Study of Malicious Code in PyPI Ecosystem
by siddheshgunjal on Friday September 08, 2023 @10:35PM
(#37441660)
So, is there a way to check if any malicious packages installed in my conda environment?
[ Parent
| on HN ]
Re:A Study of Malicious Code in PyPI Ecosystem
by ashishbijlani on Friday September 08, 2023 @11:04PM
(#37441839)
I've been building Packj [1] to detect dummy, malicious, abandoned, typo-squatting, and other "risky" PyPI/NPM/Ruby/PHP/Maven/Rust packages. It carries out static/dynamic/metadata analysis and scans for 40+ attributes such as num funcs/files, spawning of shell, use of SSH keys, network communication, use of decode+eval, mismatch of GitHub code vs packaged code (provenance), change in APIs across versions, etc. to flag risky packages.
Re:A Study of Malicious Code in PyPI Ecosystem
by siddheshgunjal on Friday September 08, 2023 @11:40PM
(#37442056)
This is interesting! Implementing it today itself for my open source package development pipeline!
Re:A Study of Malicious Code in PyPI Ecosystem
by thenerdhead on Sunday September 10, 2023 @05:50PM
(#37460435)
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?
Re:A Study of Malicious Code in PyPI Ecosystem
by ashishbijlani on Sunday September 10, 2023 @09:19PM
(#37461747)
Thanks! We need more such efforts to improve supply-chain security of open-source software.
Packj detects typo-squatting (impersonation) as well.