University libraries are being swarmed by AI bots, putting public access at risk
Posted by blakesterz 4 hours ago
Comments
Comment by Bender 4 hours ago
Comment by sixtyj 3 hours ago
But there are bad actors - bots that try every possible urls and traversals and cross scripting and so on… I see it in our access logs. This cannot be solved otherwise than some greylisting/blacklisting on ISP level. E.g. this is so huge that we have started to block all Chinese inbound traffic. I am sorry for that because Deepseek and other good actors are probably blocked as well but IP rotation made it impossible to filter bad ones only… (and I suppose that DS uses EU or US addresses as well so they shouldn’t be blocked in full).
Comment by Bender 3 hours ago
Indeed, they use an edge SSL Bump proxy that is already bandwidth limited and has to speak real HTTPS.
I do not focus too much on IP addresses but rather the behavior that they can not hide. LLM's can help you spot this behavior. Good LLM vs. Bad LLM. Gemini knows a few tricks but you have to coax it out of them. It seems to not want to overload people with information. That said there are some good IP lists that can be used in blackhole routing tables, nginx geo tables, etc...
Comment by sixtyj 2 hours ago
I focus on content on our site so blocking part of internet with wordfence was brute but as life has only few thousands of weeks, it was the least I wanted to think about :).
Would you mind to share a source of good IP lists pls?
Comment by Bender 2 hours ago
LLM's can help you implement iprange into IP list building scripts to keep the lists smaller and more efficient.
[1] - https://github.com/firehol/blocklist-ipsets/
Comment by sixtyj 26 minutes ago
Comment by Bender 18 minutes ago
Before pushing such things to production consider first testing in dev/qa then staging or some canary environment. I use those IP's to determine who gets into a moderator review queue so worst case it just makes more work for me. Consider using those in conjunction with whatever rate limiting capabilities your web server provides first so it is not a hard block in the unlikely event a real customer shows up on one of them.
Comment by eatonphil 3 hours ago
I could build something more complex to discover the patterns, or use Turnstile maybe. I'm not really sure at the moment.
Comment by EvanAnderson 2 hours ago
The bots may have layer 7 signatures that make them "easy" to block, but I'm dealing with COTS software with no ability to make changes to the stack. Even if I could by the time they're blocked the work is done and they're never coming back anyway.
I don't think I'm seeing the LLM bots in the scraping on this particular site. This site's data is highly sought-after by data brokers, legal services advertising, debt collectors, etc. I tend to think I'm seeing homespun scrapers. This site has been up for 20+ years and the scrapers seem to be well-adapted to using the HTML as an ad-hoc API for the data. The difference in the last few years has been the availability of vast numbers of residential proxies to mask the traffic.
Comment by Bender 3 hours ago
Comment by eatonphil 3 hours ago
Some of the things that seemed like they'd cut out lazier bots/scripters involved browser fingerprinting that I didn't want to yet have to deal with disclosures or approval for. But also even some of these browser fingerprinting things were disable-able via flags when you start up Chrome or whatever.
I think what would work overall is to track all requests for a pattern of page access and start blocking other systems that are part of that pattern. But that also wouldn't account for like... landing on the front page of HN, which happens not infrequently.
All of this is aside from per-IP or per-user proof of work. Whenever someone lands on a more expensive page I make the browser do proof of work and store it in a cookie, unique to the IP or user. (Signed in users don't have to do proof of work). This is a perfect solution except for the IP rotation I'm talking about above.
edit: ah also, I don't do SSL termination so can't spot the SSL configuration. But Cloudflare does. And all of this is even after Cloudflare paid bot traffic systems are in place.
edit 2:
> tiny percentage of bots will still get through but the load becomes much more manageable.
The load is not the problem. It's only at most a few bot hits per second. I'm just having trouble removing bot attribution from view counts.
Comment by twosdai 2 hours ago
Youtube wont count a view until you watch for some percentage of the video. Maybe consider something similar.
Comment by eatonphil 2 hours ago
Comment by Bender 3 hours ago
I love sharing methods with the botters so they step up their game, thus forcing me to step up my game. Everything I use does not require javascript, cookies or authentication. I save authentication as a last resort which means I lost that round.
Botters are welcome and encouraged to test their setup on my silly hobby sites. Here's one of them: [1]
[1] - https://altchan.org/sh/33
P.S. These are the simplest crude methods for the obvious bots, let your LLM to help spot the fakers. pre-2026 Safari will not work. Do not visit image boards with unpatched browsers.
Comment by dmtroyer 1 hour ago
Comment by Bender 59 minutes ago
I was told that I could only lead a horse to water but I could not make it drink. Turns out that was not at all true. I had to find which horse was being the ass and re-educate it so the yearlings could get to the water.
That said I think most people here can at very least have discovery conversations with LLM's to explore their options. They can share their architecture, infrastructure design and have LLM's walk them through gathering more information. It may be bumpy at first but I suspect some of them will be able to give the bots a few flat tires. I have confidence that necessity will drive innovation and they most likely will not even have to spend a dime.
Comment by blakesterz 3 hours ago
Comment by qingcharles 3 hours ago
The problem with the libraries is that all these scans are behind walls, so while the texts are public domain nobody can easily access them. I'm trying to liberate them and re-upload them outside the walls.
Until recently a lot of libraries would allow you to remotely sign up for a library card, but in the last 12 months almost all of them have reverted to having to bring ID in person to the library to validate your account, which puts the brakes on things.
Comment by NoMoreNicksLeft 45 minutes ago
Are you doing newspapers?
Comment by TazeTSchnitzel 3 hours ago
Comment by oasisbob 2 hours ago
- Residential proxy providers
- Hosting providers with IP-rotation as a service.
- Hosting providers who chase AI training customers, DigitalOcean is a big one
- Clouds like AWS with headless browsing as a service
- Platforms like Replit whose value proposition starts to fall apart if clients can't make requests from their platform.
- Companies like meta, whose existing bots are now obviously completely unchained from their advertised responsibilities
Comment by joe_the_user 1 hour ago
This is the way for companies these days to avoid legal responsibility for their actions - hire a contractor on a "don't ask, don't tell" basis.
Of course such things are extra-ironic in the context of US companies complaining about having their condensed by Chinese companies.
Edit: I read this in one article a while back. I can't links either corroborating or refuting it now and I think that's again because whatever the companies do, they want to keep it hush-hush.
Comment by londons_explore 1 hour ago
I just make sure all my pages are super lightweight to cache and serve from cloudflare and let the bots do what they like.
If I put something on the internet for all to see, I want bots to be able to see it too.
I've been on the other side of bot blocks - when I ask my LLM to buy me X and it comes back and says the only place it could buy from is some Bulgarian seller because everywhere else has anti-bot scripts, I make sure to give that Bulgarian site my business.
Comment by engineer_xyz 1 hour ago
Comment by seemaze 1 hour ago
Can we re-deploy the internet as statically hosted data available through a defined api? Something like DNS for data; eventually consistent and evenly distributed. Either the data is open and ubiquitous, or closed and inaccessible.
Comment by sneak 1 hour ago
https://git.eeqj.de/sneak/smallwebwaf
It’s alpha but it should be ready for real-world testing in the next couple of days. I’m going to drop it in front of my Gitea and home-grown api servers.
I’m super tired of Anubis spamming me with furry fetish art on its pointless interstitials 20 times a day. As someone pointed out in another comment, LLM scraper bots are super easy to detect with basic heuristics. PoW and session cookies and an interstitial are massive overkill and annoying spam.
Comment by jdw64 2 hours ago
[1]https://www.makonea.com/en-US/casual/scraping-bots-are-destr...
Comment by pfdietz 2 hours ago
RIGHT?
Comment by talon8635 1 hour ago
Comment by tacocataco 3 hours ago
Comment by benjismith 3 hours ago
"Open Access" means supporting users. Now your users are also bots, and the people that deploy those bots. You need to be able to serve those users too.
Comment by iberator 1 hour ago
Comment by tokai 3 hours ago
Comment by robcohen 3 hours ago
Comment by Driver8 1 hour ago
If you believe that they should focus on the scalability required to handle bot traffic perhaps you would be best donating money to them to help give them the resources to be able to do that, or volunteering to try to help understand their problem and fix it if you believe that it's a skill issue.
Reframing what you said in a more positive way could be: - I wonder what architecture they used for this and how it could be improved? - I wonder what resource limits they have that prevent them from handling this issue? - I wonder whats unique to a library that limits their ability to do what tech companies do?
Comment by mcmcmc 2 hours ago
Comment by hedora 2 hours ago
Comment by sdellis 1 hour ago
Comment by mcmcmc 53 minutes ago
First function is archival and preservation, second is access for university students and researchers. It’s not Anna’s archive or TIA
Comment by j45 3 hours ago
Comment by hedora 2 hours ago
If anything, libraries should be becoming more AI friendly, not less. Instead, we get this sort of bullshit from the ACM:
https://dl.acm.org/doi/10.1145/3832783.3834511
It's a canonical DOI on what was a download server. It says exactly which file is being requested. (I chose a random recent one.) At the very most, they should serve a static page with a bibtex entry, and a few other metadata fields, and a link to the PDF and whatever other formats are available.
Instead, we get piles of captchas, login-gate spam about how they're "open access" now and have some initiative to be LLM friendly.
Getting back to the problem of people doing stuff that requires access to library materials: What sort of server-side cost multiplier do you suppose this ACM page has vs. just serving a few S3-compatible URLs that point to a few mirrors? (Or, got forbid, Anna's Archive / libgen, since ACM is open access, and those sites would be doing nothing wrong by mirroring ACM content.)
Comment by blakesterz 2 hours ago
Comment by hedora 2 hours ago
Also, if they just turned off all the user-hostile crap, they'd probably get at least 1000x back on their serving costs. How much does it cost to serve a login gate, captcha and rejection screen vs. a ~1MB static file?. What about the human cost where actual users cannot get access to the data they should have access to?
Just now, I ran a Kagi search. Its LLM summarized some page on the internet, but when I went to check the reference, I got a "sorry, humans only" access denied error message. I guess it's good that I could ask the LLM to quote the document verbatim for me in a follow up message, but what fresh hell is this? (Also, the error message screen was clearly longer than the document I'd requested.)
Comment by piltdownman 2 hours ago
After Pulte fired an employee represented by the union, LIUNA urged members to call and send email to the company, expressing their opinions. As a result of the increased traffic, the company's email system crashed. The Sixth Circuit ruled that the LIUNA's instruction to call and email "intentionally caused damage," reversing the lower court's decision.
Now thankfully we have Sandvig v. Barr, 2020 where the DC Federal Court ruled that the CFAA does not criminalize the violation of a website's terms of service, but imo all bets are off in terms of interpretation of the law in the wild west of AI.
Comment by hedora 2 hours ago
I suppose this is one of those laws that doesn't apply if an individual is a victim? I have a email box that sometimes fills with spam and rejects legitimate email. Can I get the corporations that filled it up to be charged with felonies?
Comment by piltdownman 2 hours ago
(1) They admitted its Claude models had breached the systems of three companies since April; including Huggingface.
https://www.bloomberg.com/news/articles/2026-07-30/anthropic...
(2) They secured unauthorised access to a U.S. state government website hosting election-related data, pulling aggregate vote-count statistics from a gated government dashboard. The state government itself confirmed the access was entirely unauthorised.
https://seekingalpha.com/news/4657023-anthropics-claude-bypa...
If a human security researcher had deployed an agent that behaved this way, it would constitute a textbook felony under the CFAA for accessing those systems without authorisation.
Unfortunately different rules apply when you have the power to buy off Congress and the Appeals Courts.
Most recently a US appeals court ruled on 5 August that Amazon was unlikely to succeed on a claim that Perplexity's AI agents violated the Computer Fraud and Abuse Act by covertly accessing private Amazon customer accounts.
https://www.rte.ie/news/technology/2026/0807/1586941-artific...