Malicious Python Packages Replace Crypto Addresses in Developer Clipboards

Re:Malicious Python Packages Replace Crypto Addresses in Dev... by louislang on Monday November 07, 2022 @02:46PM (#33511300)

Awesome seeing this posted! Full disclosure: I'm a co-founder at Phylum.

This campaign is ongoing. Our system just notified us of two more packages, which have been reported to PyPI. I expect this list to continue to grow throughout the day.

As a related aside, we are working on a package sandbox that prevents access to disk, network and env variables during package installation. It's not quite ready for primetime, but it is completely open source and we'd love some early feedback/contributions!

https://github.com/phylum-dev/birdcage

If anyone has any questions, I'd be more than happy to answer them!

[ Parent | on HN ]

Re:Malicious Python Packages Replace Crypto Addresses in Dev... by a-dub on Monday November 07, 2022 @03:17PM (#33511757)

interesting read. i was a bit confused at first, thinking that the malicious package names were being inserted into cut and pasted pip/apt/etc install strings. i see now that's not happening in this scenario, but curious if that behavior has ever been observed.

[ Parent | on HN ]

Re:Malicious Python Packages Replace Crypto Addresses in Dev... by louislang on Monday November 07, 2022 @03:24PM (#33511851)

We haven't seen this particular sort of thing just yet in packages. There was a similar attack from a few years ago called "pastejacking" that did something directionally similar to what you're suggesting though!

[ Parent | on HN ]

Re:Malicious Python Packages Replace Crypto Addresses in Dev... by eddsh1994 on Monday November 07, 2022 @02:58PM (#33511483)

Cool project! Phylum looks useful at addressing a few worries I have with Python. Would it work in a mostly air-gapped environment, or does it have to call home regularly?

[ Parent | on HN ]

Re:Malicious Python Packages Replace Crypto Addresses in Dev... by louislang on Monday November 07, 2022 @03:02PM (#33511553)

We are basically ingesting and analyzing every package as it gets published to the various ecosystems (currently NPM, PyPI, Rubygems, Maven and Nuget; Go and Crates support landing in beta soon).

This is currently offered as a SaaS solution, but we'll be providing an on-prem offering by EOY that should work well in an air-gapped environment.

The sandbox I mentioned above is rolled into our CLI by default, but that should operate well enough on its own without needing to call out to our API if you wanted!

[ Parent | on HN ]

Re:Malicious Python Packages Replace Crypto Addresses in Dev... by eddsh1994 on Monday November 07, 2022 @04:23PM (#33512686)

Thanks Louis, I’ll keep an eye out for it!

[ Parent | on HN ]

Re:Malicious Python Packages Replace Crypto Addresses in Dev... by louislang on Monday November 07, 2022 @04:37PM (#33512879)

no problem, happy to chat whenever!

[ Parent | on HN ]

Re:Malicious Python Packages Replace Crypto Addresses in Dev... by pabs3 on Monday November 07, 2022 @09:16PM (#33515194)

How does Phylum detect these issues? I guess you have a mirror of PyPI and run some kind of scanner over all the code?

[ Parent | on HN ]