
Petlibro Security Flaws: Your Feeder Can Be Hacked Today
A security researcher disclosed six API vulnerabilities in PETLIBRO’s platform in late 2025, including an authentication bypass that lets anyone sign into any account that uses Google login. Two months after he reported it and took a $500 bounty, the researcher said the vulnerable endpoint was still live. In a separate incident, an 805-upvote Reddit thread documents a PETLIBRO RFID feeder opening for a cat’s implanted microchip, sending the owner to the vet with a $1,000 bill. Five checks before you put another cloud-connected feeder in your home.
I spent an afternoon with the disclosure, then with the r/netsec thread that carried it (223 upvotes), then with the owner threads it connects to. The findings are technical. The risk is not. A feeder sits inside your home network, holds a microphone in some models, records feeding audio in others, and answers to a server you do not control. When the server has holes, so does your house.
What did the security report find?
The short answer: six flaws, and the first one is the one that matters. The researcher, writing at bobdahacker.com under the title “Petlibro: Your Pet Feeder Is Feeding Data To Anyone Who Asks”, walked through each:
| # | Flaw | What it allows |
|---|---|---|
| 1 | Social login auth bypass | Sign into any account that uses Google login |
| 2 | Pet data unauthorized read | Pull any pet’s data by ID |
| 3 | Device serial + MAC leak | Read any device’s identifiers |
| 4 | Device hijacking | Take over a device by serial number |
| 5 | Feeding audio leak | Bulk-download private feeding recordings (sequential audio IDs) |
| 6 | Shared-owner add | Add yourself as owner of any device |
On the bypass he was direct:
Their social login API at /member/auth/thirdLogin doesn’t verify OAuth tokens… anyone can still take over any account that uses Google login… This is still working as of today.
The timeline matters as much as the flaws. Reported November 5, 2025. A $500 bounty paid. A request to sign an NDA. Then the December 27 write-up with the vulnerable endpoint still live, two months later. r/netsec commenters drew the obvious parallel: “Lovense situation all over again.”
For a pet owner, this is the second half of a story we already covered. The August 2026 outage showed what happens when PETLIBRO’s servers go down: feeders stop, meals get missed, and the brand’s “vast majority” wording does not feed the cats in the minority. This disclosure shows the other failure mode. The cloud is a liability twice: when it fails, and when it leaks.
The $1,000 microchip mix-up
The short answer: a PETLIBRO RFID feeder opened for a cat’s implanted microchip, the owner rushed the cat to the vet assuming it had swallowed a collar tag, and the bill came to $1,000 including X-rays.
The thread sits on r/CatDistributionSystem with 805 upvotes and 93 comments. The feeder is sold to open only for the RFID tag on the collar; the product page says it does not detect microchips. The owner’s account of what happened:
I have the Petlibro RFID feeder, the kind that’s supposed to open only with the RFID tag, not microchips. Their website clearly says it doesn’t detect microchips. Well, turns out that’s not true. After a $1000 vet bill (yes, including X-rays), we found out that the feeder was somehow opening due to his microchip. The last 6 digits matched, and the feeder was recognizing it as a valid tag.
Two failures in one box. The reader matched a partial identifier against the tag database and treated it as a match, and the product documentation said that could not happen. If your cat carries an implanted chip and you run an RFID feeder, that combination can open the lid for the wrong cat, or refuse the right one. Our microchip feeder guide covers which readers match full chip identifiers and which lean on collar tags; the short version is to ask exactly what the reader matches before you buy.
A camera in your house, with no opt-out
The short answer: the privacy problem is not PETLIBRO-specific. It is the category’s default.
Whisker’s Litter-Robot 5 ships a camera that faces into your home. A 30-upvote r/litterrobot problem list, “Please share your problems with the Litter Robot 5 and 5 Pro”, includes “Privacy concerns about camera facing into home… no opt-out.” That is a $1,000 box, cleaning your cat’s waste, with a camera the owner cannot disable and footage the brand does not store locally.
The same pattern reaches cheaper devices. A 164-upvote thread on r/mildlyinfuriating covers an $80 “smart” fountain whose app claims to track weight, litter visits, and activity:
This is just a water fountain, mind you. No camera, no magical chip reader… How would it know all of these things? The whole thing seems kind of gimmicky to me.
That is the security angle nobody prices in. A device that fakes data collection still collects data. Every “smart” feature is an endpoint: a server, an account, a database row. And subscription walls run on the same architecture with billing attached. The r/Pets thread on cameras that “slide in the subscription after 30 days” notes the sellers “always keep it pretty hidden.”
What a hacked feeder actually costs you
The short answer: not just a stolen account. Feeding audio recordings, device control, and a foothold inside your home network.
Work through flaw #5. Audio IDs are sequential, so the leak is not one recording. It is every recording, harvested by a script. Those recordings capture your kitchen, your schedule, your voice. Flaw #4 turns the device itself into someone else’s property; for a feeder, that means they can drop meals or withhold them. A hijacked IoT device is also a standing position on your home network for anything else an attacker wants to reach.
Then there is the quiet cost the microchip story shows: confusion. The owner spent $1,000 and a day at the vet because the product behaved in a way its own documentation ruled out. You cannot budget for that, because nobody prices it.
Five checks before you buy
The short answer: these five, in order.
- Where does the data live? Local storage beats cloud, full stop. A camera that records to an SD card with no subscription keeps footage out of any vendor database. Cloud-only recording means the vendor holds your home video.
- Can it work without the account? Ask whether the schedule lives on the device. The PETLIBRO local-scheduling failure proved the difference: device-stored schedules feed, server-triggered ones miss meals.
- What does it record, and can you opt out? List the sensors: camera, microphone, feeding audio. Then ask if each can be disabled. If the answer is no, assume it records everything, always.
- Is there a disclosure path? A real one: a security contact, a bounty, published advisories. The PETLIBRO pattern, bounty paid, NDA requested, endpoint left live for two months, is the opposite.
- Does the camera face your home? Placement is a security feature. A camera covering the litter box covers the hallway, the door, and your schedule. A physical shutter or cover beats any software setting.
Already own a smart feeder? Do this now
The short answer: four moves, five minutes each, and none of them cost money.
- Drop social login. The disclosed bypass sits in the Google-login path. Switch the pet account to email plus a unique password, not a password you reuse elsewhere.
- Audit the owners list. Open the app’s sharing or family settings and remove anyone you do not recognize. Flaw #6 means an attacker can add themselves as a shared owner.
- Cover the camera and the mic. A piece of tape on the lens beats any privacy toggle. The LR5 owners who cannot opt out of the camera have no equivalent option, so do it before the firmware changes.
- Test offline feeding. Kill the Wi-Fi for 24 hours and watch whether meals dispense. If they do not, that machine cannot be your only feeding plan while you travel, as the outage taught owners.
What should you buy instead?
The short answer: PetSafe Smart Feed for feeders, TP-Link Tapo C210 for cameras. Both are the low-attack-surface picks in their categories: no subscription, local operation, and nothing in them that records your home.
The PetSafe Smart Feed (on Amazon, about $120.99) has no camera, no microphone, no feeding audio, and no subscription. The schedule lives on the device, so it feeds when the internet does not. It is the same pick in our feeder comparison and the reputation showdown, and it is where our PETLIBRO feeder review lands: the least connected feeder that still feeds on time.
The TP-Link Tapo C210 (on Amazon) has no subscription, and microSD recording keeps footage out of the cloud entirely. The full review and the no-subscription camera guide cover setup and limits. A camera that records to a card in your hand is a camera with no vendor database to leak.
No brand in this category is a fortress. The goal is fewer attack surfaces: no camera pointed at your hallway, no microphone in your kitchen, no server that can go down or get broken into. Run the five checks against whatever you are considering, and treat “works offline” and “records locally” as the features that matter most.
Updated: August 28, 2026. Sources: bobdahacker’s PETLIBRO disclosure and its r/netsec thread (223 upvotes), the r/CatDistributionSystem microchip thread (805 upvotes), the r/litterrobot problem list (30 upvotes), the r/mildlyinfuriating fountain thread (164 upvotes), and the r/Pets subscription thread. Security status and prices change; verify before purchase.
FAQ
Can my PETLIBRO feeder really be hacked? A researcher disclosed six API vulnerabilities in late 2025, including an authentication bypass that signs into any account using Google login, pet-data reads, device hijacking by serial number, and bulk access to feeding recordings. He reported them on November 5, took a $500 bounty, and was asked to sign an NDA; his December 27 write-up said the vulnerable endpoint was still live two months later. PETLIBRO has not published a security advisory, and we could not confirm the current status of every endpoint.
Was the PETLIBRO vulnerability fixed? PETLIBRO has not published a fix timeline or security advisory. The researcher’s December 27, 2025 write-up states the vulnerable social-login endpoint was still live two months after his November 5 report. We could not verify the current status of every endpoint from public sources. Until the company publishes details, treat the account as exposed: avoid Google login for the pet account, use a unique password, and remove unknown shared owners from the app.
Do other smart pet devices have these problems? The pattern is category-wide, not brand-specific. A 30-upvote r/litterrobot list documents a Litter-Robot 5 camera facing into the home with no opt-out. A 164-upvote thread documents an $80 “smart” fountain showing weight and activity data it has no sensors to measure. Cameras that “slide in the subscription after 30 days” are common enough to have their own threads. The safest devices are the boring ones: no camera, no microphone, local storage, no mandatory account.
Which smart pet feeder is the most secure? The PetSafe Smart Feed (about $120.99) has no camera, no microphone, no feeding audio, and no subscription; the schedule is stored on the device, so it feeds without the internet. For cameras, the TP-Link Tapo C210 records to a microSD card with no mandatory subscription, which keeps footage out of any vendor database. Neither is a fortress, but both have the smallest attack surface we have tested in each category.
Does the microchip misread affect all RFID feeders? The documented case is a PETLIBRO RFID feeder that opened when a cat’s implanted microchip partially matched a tag ID (last six digits), despite the product page saying chips are not detected; the owner’s vet bill came to $1,000 including X-rays. Whether other readers behave this way depends on what they match: full ISO chip identifiers or short partial matches. Ask the seller exactly what the reader matches before buying, and test with your cat’s chip if you can.