11 ms·
Over 100k Infected Repos Found on GitHub
- thsksbd 3y ago[flagged]
- sigmoid10 3y agoI've noticed these too by randomly stumbling over similar repos. I usually don't run code from random repos, but now I have reached a point where I spin up a sandbox vm even when I trust the repo and the owners. If you are a dev today, you should probably have at least thee firmly separated environments for work, hobby and personal stuff.
- Ringz 3y ago> If you are a dev today, you should probably have at least thee firmly separated environments for work, hobby and personal stuff. The complexity of digital life takes on dimensions that make me doubt whether it can continue in the long term.
- sigmoid10 3y agoI think this is just another opportunity to create new services. I've seriously considered moving all my stuff (except gaming) into something like apache guacamole. I'm already used to remote dev-ing over ssh and once you can easily get your desktop anywhere without even needing a client, there's no real reason to run everything on the one system you happen to be sitting at. And if internet connectivity is still an issue in your country you could even run this setup locally. Maybe find a way to sync it with a remote system. I'm pretty sure this is the future anyways.
- geraldhh 3y ago> there's no real reason to run everything on the one system you happen to be sitting at theoretically. in practice the added latency is a problem outside of casual use. update: clarification seems to be neccessary as i was talking about audio/video/gaming type workload, NOT office stuff
- hhh 3y agoCan you give an example? I haven’t ran anything for work on my Macbook locally in a long time.
- rcbdev 3y agoThe latency issue is increasingly disappearing or at least becoming negligible in most population centers. For example, in my country almost every company uses Citrix (no affiliation) or similar workspace solutions, where the entire workstation is virtualized in a data center and you only access via a thin client. Entire nations of people work like this already. Cloud gaming will probably be the next frontier in this.
- BlueTemplar 3y ago(Real time) cloud gaming only works with a very low latency internet connection, which requires wiring, which leaves out most of the non-city users (and still some city ones). Not to mention that it's ridiculously wasteful.
- google234123 3y agoWhat percent of consoles/gaming pcs are being used for gaming in average per hour? 15%?
- jack_pp 3y agoI'd say it's rather more wasteful for everyone to have expensive rigs to play games a couple of hours a day when we could share computing resources in the cloud
- 63stack 3y agoI would love to have this, but this is very naive in the current economic climate. There is already a notion of trying to get rid of general computing devices from Apple, Google, and Microsoft. They would immediately use the opportunity to corner the market, lock down everything, and start extorting more money. There is no way I would give up my personal desktop.
- KronisLV 3y agoI remember using a variety of VNC/RDP over local network for connecting to my laptop, so I could do development there and keep the codebase completely separate from my other machines, while still using my desktop keyboard, mouse and larger monitor. I'd just turn it on, connect to it and treat it as another window in the OS. That said, I think we either need proper OS level sandboxing, something like Qubes or just using multiple VMs or devices with remoting. It doesn't feel viable to have something like Discord or other communication software or things with account tokens, and executables like software or games running on the same install, whereas dual booting isn't viable for that either.
- avgcorrection 3y ago> I think this is just another opportunity to create new services. So maybe cool for people with itches or startup aspirations, more hassle for everyone else.
- overstay8930 3y agoDoes nobody use VMs anymore? I just spin up EC2 instances with Shortcuts on my Mac and destroy them when I’m done. Run a bash script to save my work to s3. Are people just doing everything locally or something?
- flyinghamster 3y agoIndeed. My parents (age 80+, father was an engineer and gadget freak) flatly refuse to use smartphones. My dad has a bit of trouble with the new big-screen TV but can figure things out. My mom just can't cope with the new remote and user interface. My dad's enough on the ball that he doesn't fall for scams, but I despair for people who aren't prepared for this (or who don't realize that email is untrustworthy). All this digital stuff falls naturally to me, but for the most part, people my age and older really don't cope well with the digital world. I'm an exception because I got my feet wet in the mini/timesharing environment, just as personal computing was beginning to take off, and didn't lose interest. Also, how well are we really teaching the next generation? I see both good and bad in that regard, with Pi, Arduino, etc. being the brightest spot, and locked-down ecosystems and pervasive surveillance the darkest. And, of course, there's the whole culture problem. The notion of "computer literacy" went from "knowing how to use a computer" to "knowing how to use Word and Excel" almost overnight. Are schools actually using things like the Pi and Arduino, or are we leaving it to parents to get such things into their hands?
- Shared404 3y ago> Are schools actually using things like the Pi and Arduino, or are we leaving it to parents to get such things into their hands? Gen Z here checking in to say almost entirely the latter :/ . Some schools have an elective that would get things into the hands of kids, but nowhere near 100% and they generally have a pretty low coverage of students at the school.
- yjftsjthsd-h 3y agoEvery year, qubes looks more reasonable:)
- fsflover 3y agoSounds like a good reason to use Qubes OS, where everything runs in VMs by default (my daily driver).
- prmoustache 3y agoMy experience with Qubes OS had been so so last time I've tried it. Have they managed to get rid of Xorg and the terrible screen tearing issue that should be a thing of the past in 2023? I remember there was a project named SpectrumOS that tried to do something similar to QubesOS but with nixos, crosVM and wayland. AFAIK the project stalled. I am using a sort of middle ground between traditionnal desktop and QubesOS. I run a number of VMs on my machine for different purpose and use waypipe to start apps as individual windows on the main desktop. I don't really have the copy/paste separation that QubesOS has, nor a separation between host and network VM but at least I can separate duties, filesystems and seamless windows showing on only one desktop. To distinguishes the browser and terminal windows I use different themes.
- fsflover 3y agoAre you using an Nvidia GPU? https://github.com/QubesOS/qubes-issues/issues/5104 https://github.com/QubesOS/qubes-issues/issues/5104 https://github.com/QubesOS/qubes-issues/issues/7591 https://github.com/QubesOS/qubes-issues/issues/7591 If not, try this: https://github.com/QubesOS/qubes-issues/issues/6880#issuecomment-1321045422 https://github.com/QubesOS/qubes-issues/issues/6880#issuecom... There is no tearing on my Librem laptops.
- prmoustache 3y agoNope, but regarldess of drivers, xorg has never been pixel perfect and tearing do happens. You are just probably used to it but it is obvious once you have started using wayland how smoother your desktop becomes. It is the first time I hear about that Tearfree option and I am wondering. If it exists and it isn't the default behavior, it means there must be some annoying drawbacks right?
- jbverschoor 3y agoCheck out container-shell [1] it is one of the use cases. Not a VM but a docker container. Chroot a directory in a container, and does some automatic house keeping etc [1] https://github.com/jrz/container-shell https://github.com/jrz/container-shell
- AlienRobot 3y agoA link to a github repo? How do I know it's not infected?
- jbverschoor 3y agoIt's a single bash script
- simonjgreen 3y ago> If you are a dev today, you should probably have at least thee firmly separated environments for work, hobby and personal stuff. I hate to call it out, but, isn’t that table stakes? Blending work and personal environments should be an obvious no. Are employers out there ok with this?
- TaylorAlexander 3y agoI used to work at Google where all computers were militantly segregated from non work stuff. Now I run a little non profit robotics org with one other person, and when I work from home I just use my personal desktop with no separation. It depends on where you work, how much people will care and whether there are resources to do anything about it.
- tsbinz 3y agoBig employers (at least the ones I know) aren't regarding work, I guess with smaller ones it maybe is, especially with BYOD? I think the issue probably isn't uncommon for freelancers/contractors too. Hobby and personal stuff I think a lot of people mix, I don't use the machine where I do bank/tax/etc stuff for hobby work, but I'm not sure that's common.
- deleted 3y ago[deleted]
- avgcorrection 3y agoOK Drone.
- fubar34 3y ago[dead]
- lopkeny12ko 3y agoI do this now today too, but not even for potentially malicious software. Some projects that are not inherently malicious are just written poorly or stupidly by design. Just the other day I ran a program that, before I even requested it to do anything, appended 3 lines to my ~/.bashrc. I didn't even notice until days later. I can't fathom why any developer thinks this is a good idea, and is exactly the kind of thing that makes me sandbox every foreign piece of code I run now.
- Ringz 3y agoDespite its possibilities, GitHub cannot prevent all this - what happens to the other providers such as Codeberg, etc.?
- vaylian 3y ago> Despite its possibilities You mean despite its (financial) resources?
- glaucon 3y agoI don't know but I guess the smaller fish are protected by virtue of them not being worth the automation effort. A bad actor can spend a lot of time and effort attacking Github and have their efforts exposed to so many more developers than the same sort of effort on, say, Codeberg would achieve.
- arp242 3y agoAnd you'd be shooting yourself in the foot anyway. At "codeberg scale" it's possible to entirely take over the platform with spam and malicious repos, at which point codeberg will implement drastic limits to prevent this like manual account verification or some such, which will stop it. It would be an enormous waste of time for everyone.
- Animats 3y agoSo who's behind this? Who's doing something about it? Where's Homeland Security on this? This is their job. This is an attack. "The ease of automatic generation of accounts and repos on GitHub and alike, using comfortable APIs and soft rate limits that are easy to bypass, combined with the huge number of repos to hide among, make it a perfect target for covertly infecting the software supply chain. This campaign, along with dependency confusion campaigns plaguing package registries and generally malicious code being spread through source control managers, demonstrates how fragile software supply chain security is, despite the abundance of tools and available security mechanisms."
- DinaCoder99 3y ago[dead]
- toppy 3y agoWhere's GitHub Fraud Detection Team?
- andreashaerter 3y agobusy blocking the co-founder https://twitter.com/defunkt/status/1754610843361362360 https://twitter.com/defunkt/status/1754610843361362360
- arp242 3y agoThat sort of thing happens because there's so much spam and malicious activity, such as the thing reported in this story.
- namaria 3y ago> how fragile software supply chain security is, despite the abundance of tools and available security mechanisms There seems to be a fundamental trade-off at play. I often see security portrayed as a hindrance, requirements thereof as a drag on productivity. That is in line with a strong trend in developers with a very narrow skill set. The ability to throw framework at the wall and see what sticks pays very well. No one wants a stick in the mud asking why on Earth dependency management is at the state it is, or imposing reasonable security practices. I have been there, I have argued with developers from teams that had been breached before saying "no, this is safe because I can't see how this could be exploited". Security by obscurity so deeply ingrained one takes obscurity from oneself as evidence of safety.
- zavaz 3y agoA simple case of marking these officially would get some attention.
- rwmj 3y agoAnd later, Github could start selling these blue ticks. What could possibly go wrong? /s (I do agree with your point that Github should be better at displaying which repo is the official one for a project.)
- dgellow 3y agoWhat tooling are you people using to avoid that type of issues at your workplace? And are you satisfied with your setup? We are a pretty small team developing SDKs that have a pretty large amount of weekly download. I’ve been evaluating tools such as snyk, aikido.dev, and some solutions built on top of renovate (that we already use for general dependency management), it’s not obvious if they would help with this, and given we are still tiny dealing with a large amount of false positive (that was the case with snyk) is a pain. Just curious how others are dealing with this.
- chha 3y agoWe tend to avoid using github repos, but go for published packages from the usual sites; Nuget, Pypi, Npm etc, using Repository and Firewall from Sonatype to act as a proxy between us and the package repos. All packages are analyzed and tagged with various metadata by Sonatype. Firewall lets us define policies for what we can use, and will filter out everything else. This only works for published dependencies, but based on a couple years experience it works really well. No issues with malware (so far), we don't let packages with known vulns into our codebases and we are notified if a vuln is discovered in something we use.
- alentred 3y agoYou may look into Trivy [0] , works very well for me so far. [0] https://trivy.dev/ https://trivy.dev/
- richbell 3y agoAs far as I know, Trivy only flags known vulnerabilities and would not protect against supply-chain attacks like this.
- prmoustache 3y agoTrivy only do a CVE / package version mapping. It will not tell you you are using a malicious package from an unknown repo because of typosquatting or bad practices.
- Pepe1vo 3y ago
- kangabru 3y agoI've been gradually improving my dev setup security over the past few months based on continuous reports like this. Here are things I'm trying out to improve my setup: - Use VSCode dev containers for development [1a]. Once you've created one once then they're quite easy to use and you don't need much Docker knowledge - it just needs to be installed. It's perfect for spinning up web/console apps but I had trouble with other stuff like Flutter and Electron. - Similarly I got familiar with GitHub Codespaces for smaller projects [1b]. I've done live coding in an interview before (where I had to modify a simple Node project) and I would absolutely use containers/codespaces for anything like that these days [2]. You can spin one up straight from any GitHub repo page and they're easy to work with. - Read the OWASP guidelines regularly for things like npm, Node, and Docker best practises. e.g. for Docker use the smallest image you can (Alpine) and use explicit Docker image tags [3]. - Review npm/python packages before installing them using socket.dev - it shows a full dependency security overview for things like env variable access, network calls, supply chain attacks, recent code ownership changes etc. You can also disable postinstall scripts globally as suggested by OWASP [4]. [1a] https://code.visualstudio.com/docs/devcontainers/create-dev-container https://code.visualstudio.com/docs/devcontainers/create-dev-... [1b] https://github.com/codespaces https://github.com/codespaces [2] https://www.welivesecurity.com/en/eset-research/lazarus-luring-employees-trojanized-coding-challenges-case-spanish-aerospace-company/ https://www.welivesecurity.com/en/eset-research/lazarus-luri... [3] https://cheatsheetseries.owasp.org/cheatsheets/NodeJS_Docker_Cheat_Sheet.html https://cheatsheetseries.owasp.org/cheatsheets/NodeJS_Docker... [4] https://cheatsheetseries.owasp.org/cheatsheets/NPM_Security_Cheat_Sheet.html#3-minimize-attack-surfaces-by-ignoring-run-scripts https://cheatsheetseries.owasp.org/cheatsheets/NPM_Security_...
- begueradj 3y agoLess than 1 year ago, a repository with a Trojan horse virus: https://github.com/orgs/community/discussions/63603 https://github.com/orgs/community/discussions/63603
- olabyne 3y ago> The repository [...] claims to be a password stealer > However, when I downloaded and Extract it,[...] it stole my personal information and files. Well, I don't see where is the problem here. The repo is doing exactly what it claims
- AlienRobot 3y agoI have always wondered how do these malicious actors with their bots manage to do so much. Do they ever get caught? It's like there is no deterrent. For example, if you use bots to spam Wordpress blogs with comments that contain links to your site (black hat SEO), that is obviously a bad thing to do, but I'm not sure if it's even against a law.
- kristopolous 3y agoThis sounds solvable with some kind of painful to write and test heuristic tool. Something like "find other repos with similar product names and similar code but no forking audit trail" ... If you do an automated code diff and find it's involving say, posting stuff to a server, you can become suspicious. All these signals can become rather shallow with the right tooling centralizing this would make it a bit more efficient because you can just cache things and respond fairly immediately
- pizzafeelsright 3y agoTo do so Microsoft needs to act as the strong man with a heavy hammer.
- pantulis 3y agoIn the good old days you could check the MD5 checksums of mostly everything you downloaded. But then you had to trust the website that published the checksums themselves.
- fritzo 3y agoAnd then sourceforge was taken over by malware injectors...
- pants2 3y agoOn the flip side, you would hope that the malicious binaries in these packages have already been flagged by antivirus providers.
- Too 3y agoThat says absolutely nothing if the page serving the expected md5 sum is also compromised. With HTTPS, everything is already checked in transit, so you don’t need to verify it again. On top of that, with git, all the revisions are inherently verified as sha1 hashes. In either case, what’s inside may still be malicious if you end up on a typosquatted repo.
- blueflow 3y agoI appreciate the developments. I hope blindly pulling code from Github will be seen as the risk factor that it is.
- ChrisMarshallNY 3y agoNot just GH. People add StackOverflow snippets, pretty blindly, and pull directly from personally-published repos. I know what an unpopular opinion this is, with the HN crowd, but I think we need to completely reevaluate our dependence on dependencies. I have run into people that Literally. Can't. Write. Code, without dependencies. Their skill is at passing LeetCode tests, and googling for dependencies. Their bosses like them, because they pass the interviews with flying colors, and get results really quickly. I remember, a number of years ago, attending a meetup, promising to explain GraphQL, and, instead, it was a lecture on using a JavaScript GraphQL wrapper. I don't think that two minutes were devoted to the API, itself. I seemed to be the only person in the room, that was going "Whiskey Tango Foxtrot?" For myself, I use a lot of dependencies, but I wrote almost all of them, myself. I have spent years, building a library of SDKs and modules that I can integrate into my shipping projects. I have only two external dependencies, in my current projects. These are not ones that would kill me, if I was forced to go alone, but they do save a lot of time (an Apple Keychain wrapper in Swift, and a streaming JSON parser in PHP, for the record).
- efortis 3y agoFor NPMs you can mitigate executing malware with `--ignore-scripts` https://blog.uirig.com/getting-rid-of-npm-scripts https://blog.uirig.com/getting-rid-of-npm-scripts
- pas 3y agoinstead the downloaded malicious code runs in prod. maybe, if you are lucky, it does something strange in CI and you can catch it. the only real solution is a reputation system (like https://github.com/crev-dev/cargo-crev https://github.com/crev-dev/cargo-crev ), which of course is unfortunately barely used
- efortis 3y agoCorrect, the above mitigation is only for malware on the dev laptops and build servers. IOW, it doesn't prevent injecting the malware on your program when compiling it.
- eptcyka 3y agoProd is bad, but stealing signing keys or credentials is worse.
- zoover2020 3y agoShouldn't build servers have limited or zero network connectivity in the first place?
- deleted 3y ago[deleted]
- silverliver 3y agoModern languages make offline builds far more difficult then they have to be, unfortunately. Rust, for example, buries its off-line installer on another domain. Rust also doesn't advertise or encourage bundling dependencies. Lastly, unrestricted build scripts basically give every dependency full code execution.
- silvestrov 3y agoGithub is failing the same way usenet failed: everybody could post stuff to usenet just like everybody can create a github repository and there is nothing that sets an official repository apart from a spammers repository. When Amazon has "the everything store" as main strategic goal, they get hit by "90% of everything is junk". So they end up being a store of mostly junk. Github should figure out if their product is "a repository for everybody" or it is "I can trust this code". E.g. look at the official PG JDBC: nothing here couldn't be reproduced by a spammer. How do I know that I can trust this and that it is not an infected repos? https://github.com/pgjdbc https://github.com/pgjdbc
- hollerith 3y agoAlthough finding over 100k infected repos is not good, it does not mean github is failing because the kind of programmer who would include an infected repo can find many other ways to create an insecure product if there weren't infected repos on github.
- mgii 3y agoTo be fair, the kind of programmer who would include an infected repo is almost everyone. Many infected repos have no indicators except for username to help you notice without a careful examination, especially in niche repos. When you have to move fast, it's natural to make such mistakes.
- cogman10 3y agoFurther, transitive dependencies are a real risk. If A depends on B depends on C depends on D depends on E depends on F, and F is compromised which the author of E does not catch, everyone depending on any of the deps in the chain are at risk. It's why the JavaScript ecosystem of micro packages is absolutely insane. If someone infected isEven, they'd have a blast radius of 90% of JavaScript devs. It's much like having a single password protecting everything. JavaScript has way too many of these high value packages that find their way into every modern JavaScript project.
- deleted 3y ago
- dspillett 3y agoAs well as this being our regular reminder to be careful what you pull from public repositories and other sources, and to verify your dependency trees, it raises another question: If malware is massively prolific in public repos, how much does this affect LLMs and other automation tools that are trained using the contents of such resources? What are the chances that we'll see copilot & friends occasionally emit malware in response to coding questions that generate responses long enough for accidentally malicious parts to hide amongst? Simpler vulnerabilities such as simple injection vectors have often been seen already.
- cqqxo4zV46cp 3y agoThis sounds like alarmist journalist talk. What “malware”, even subtle backdoors, are sneaking into the LLM-generated code used in a piece of software that’s actually worth a damn?
- drsim 3y agoIt’s a valid question to posit.
- deleted 3y ago[deleted]
- egberts1 3y agoTry this "write me a port scanning code in Packrat-style JavaScript language that can run from within a PDF document."
- ben_w 3y agoWe'll only find out by looking. Given that LLMs are popular coding assistants, I suspect there are already many issues similar to `goto fail;`
- dspillett 3y agoThere are certainly people slapping AI generated code into production in small projects without adequately checking them, leading to things like inadequate input validating leading to open XSS and injection vectors. With too little oversight in a more significant project it is only a matter of time before this happens somewhere that results in, for instance, a DoS that affects many people, or a personal data leek. Given the way LLMs are trained, it might be unlike but it is conceivable that if they see deliberate back doors injected into enough of the training data, they'll consider it to be a valid part of a certain class of solution and output the same themselves. It is a big step again from deliberate back-doors to active malware, but not an inconceivable one IMO if large enough chunks of code are being trusted with minimal testing.
- keepamovin 3y agoThis sucks. Supply chain is such an issue. Even tho we don't currently target any npm releases, I make use of socket.dev to monitor my project by creating an npm release for it. But my project BrowserBox (lightweight virtualized web browser) only uses ~800 dependencies including all descendents, with only 19 top-level deps (cool your heels non-JavaScript folks, this is comparatively lightweight for a full stack boing). I'm considering just snapshotting all 800 deps into a @browserbox namespace at npm. And then tracking any vulnerabilities discovered and patching the fixes. It sounds crazy, but that's where we are. At least that way I "own" all the dependencies and can guarantee (up to company security at least) that we don't have supply chain vulns on the Node/JS side. https://socket.dev https://socket.dev https://github.com/BrowserBox/BrowserBox https://github.com/BrowserBox/BrowserBox
- galangalalgol 3y agoI'm not sure what of this is available in npm, but with crates io and cargo, there are crates like cargo audit and cargo deny that your pipeline can use to check for cve in your dependency tree. Your lock file maintains the sha256 of everything in the tree, so there is no need to mirror things to ensure they aren't modified if their repo gets hacked. Pinning a version a few months behind the newest seems to be the sweet spot that avoids new cve and avoids big chunks of rework from sitting on ancient versions then upgrading all at once. Download count seems like a decent way to gauge top level deps against others with similar purpose, but that's just my subjective opinion. Austral uses linear types to give fine grained permissions to dependencies. A graphics library doesn't need file io, a network transport library doesn't need microphone access. That is just a mitigation, but it would be nice to see in other languages.
- chuckadams 3y agonpm has “npm audit” which throws out so many warnings on nonsense like ReDos “vulnerabilities” in dev packages that everyone has learned to ignore it. It does active harm to the security of the ecosystem.
- bunderbunder 3y ago"only uses ~800 dependencies" slightly horrifies me. I was horrified to see how much time I started spending fussing with dependency hell after I moved from .NET to Java about 10 years back. And I am currently horrified by how much time I have to spend doing vulnerability updates and fussing with dependency hell in both Java and Python projects nowadays. I think maybe the reason I didn't have this problem to nearly the same extent in .NET is that .NET was relatively late to the automated package management scene. NuGet is relatively young, and, as of the last time I got paid to do .NET work, very few of the projects I worked on had actually adopted it yet. So, at least back then, .NET had a stronger culture of well-focused projects that didn't take on enormous transitive dependency trees. I would also compare this to the recent news about Boeing. Theories abound about why it's gone down the tubes. The one that I find most compelling, though, is that, over the past couple decades, they have focused on moving more of their production out to third-party suppliers, and also cost optimizing their outside supply chain. And that has made their supply chain increasingly difficult to actually manage. The details are different, but in broad strokes it looks a lot like modern software engineering culture regarding supply chain - and some have even argued that this is where Boeing got the idea. Meanwhile, the place I've worked where I found dependency management to be the least annoying - and where we had the fewest problems with quality - was a financial firm that had banned package managers for supply chain security reasons. There's something to be said for code that absolutely will not change unless you explicitly change it. I've heard similar sentiments expressed by friends and acquaintances who work at Google. We did write a lot of stuff for ourselves where others would just import a package, and that was good, too. The in-house implementation would do just what we need, and be held to a higher coding standard. So it was easier to understand, easier to debug, and easier to modify as requirements change. And here's the thing: writing it in the first place is a one-time cost, and one-time costs have good amortization characteristics. The recurring costs of dealing with code that's trying to be everything to everybody can easily be greater in the long run. They generally don't amortize; they compound. Rich Hickey really got me to see how this kind of phenomenon works in his talk "Simple made Easy." Long story short, simple is different from easy. The simpler option tends to look harder up front. But it also tends to be easier in the long run, after you give second-order effects some time to take their toll.
- bunderbunder 3y agoWe should probably assume repositories like these are part of Copilot's and ChatGPT's training data until it can be proven otherwise.
- s9df898r32h 3y agoso maybe they aren't hallucinating after all. (just using bad source info.)
- justinclift 3y agoWonder if the whole curl + sudo shell script installer thing is going to come to an end any time soon? aka the whole "just run 'curl https://somesite/install.sh https://somesite/install.sh' | sudo sh" to install our software Seems like it'd go very hand in hand with this infected stuff mentioned in the article.
- mgii 3y agoI can approve this from our findings (author of this research): our system lists around 100 instances of the pattern you've mentioned every week, and around %3 are malicious. It would be great seeing it coming to an end.
- justinclift 3y agoYeah. Security aware people have complained about this pattern forever, but then places like macOS Homebrew (brew.sh) just knowingly do it anyway. :(
- yencabulator 3y agoUnfortunately `npm i` has the same power. `go get` is the only common dependency downloader I am currently aware of where hostile code doesn't run at install or build time. I think we need better tooling for working in sandboxes, to at least compartmentalize the explosion. ChromeOS's "virtual machines can open Wayland windows on the main desktop" trick is neat, but the code needed to do that was less than clean or reusable when I last looked.
- remram 3y agoWhat's the point? You're going to ship that code to your users, or run it against your production database. If you think it might be malicious, protecting the dev laptop shouldn't be the priority.
- yencabulator 3y agoI run production services that don't even talk to a database, or that have minimal read-only access. And even for the ones with a lot of write access, having the database stolen/nuked (to be restored from backup) is quite different from handing over all of my browser cookies, or my gcloud/aws/k8s ambient authority credentials that are just sitting in a file (seriously, why is big cloud client security worse than SSH).
- EVa5I7bHFq9mnYK 3y agoImpossible. It's Open Source, watched by thousand eyes and smells of roses.
- boringg 3y agoStupid question here -- whats the most efficient way to evaluate for vulnerabilities (i.e. remove the low level risk like 95% of the cases)? Is it trust the package manager or is there another quick way?
- bee_rider 3y agoI’d love to be surprised, but I think there isn’t any way to evaluate for vulnerabilities other than read all the code (fairly carefully). I don’t think the ecosystem is set up to make it easy.
- s9df898r32h 3y agoThat's wrong because even coders can't write code without vulnerabilities inside their own software... You probably instead should use a throwaway computer (or VM if you trust them), and not do anything personal on that computer, and then burn it.
- keepamovin 3y agoLike 0ther folks say elsewhere in these threads, the most efficient way is not to eval for vulns, but to assume compromise. So, folks adopt the (admittedly ridiculous, but, in the strict sense, necessary) 0-trust step of running everything in QubesOS, then in a VM, and maybe then in Docker. Essentially each application gets its own fresh OS to fuck up or not...as it goes. I get this (but I don't condone it). It's not practical for dev purposes, only if you are endlessly testing the waters for each little thing. But, prolly, eventually we will be wowed by a shiny-thing that achieves infinity-virtualization with bare metal performance but perfect isolation so we can easiily run infinvm run github.com/malware/repo And all will be right with the world. We ain't there yet tho. Hahaha :)
- andredurao 3y agothat's funny because Wordpress sites are infected using that kind of code inject
- fl0ki 3y agoAh yes, the latest post about a marginal security concern leading neatly into an advertisement to give money to an LLM startup to address it only partially and at best probabilistically. If you're a potential customer for something like this, you quickly have to ask: why not have another 1000 contracts to separate tiny startups that each do the bare minimum to paper over an unknown portion of just one security gap? What other costs will you incur integrating with each of them in turn? How many of them will even still be in business a year later? There would be several hundred with more ROI than this one, so why start here? Even if you undertake this costly and tedious journey, how far down the list would you have to go before you get anywhere close to this one?
- throwaway290 3y agoClicking "learn more" on the cookie prompt (that covers the entire screen on my phone) leads you into an infinite loop. Not cool
- heap_perms 3y agoVery interesting read, is the jupyter notebook available?