Reddit Programming
211 subscribers
1.22K photos
126K links
I will send you newest post from subreddit /r/programming
Download Telegram
Malicious PyPI Packages spellcheckpy and spellcheckerpy Deliver Python RAT
https://www.reddit.com/r/programming/comments/1qkwrks/malicious_pypi_packages_spellcheckpy_and/

<!-- SC_OFF -->Please forgive my "Shell-check" dad joke it was too easy, had to be done. At Aikido Security we just found two malicious PyPI packages, spellcheckpy and spellcheckerpy, impersonating the legit pyspellchecker… and the malware authors got pretty creative. Instead of the usual suspects (postinstall scripts, suspicious __init__.py), they buried the payload inside: 📦 resources/eu.json.gz …a file that normally contains Basque word frequencies in the real package. And the extraction function in utils.py looks totally harmless: def test_file(filepath: PathOrStr, encoding: str, index: str): filepath = f"{os.path.join(os.path.dirname(__file__), 'resources')}/{filepath}.json.gz" with gzip.open(filepath, "rt", encoding=encoding) as f: data = json.loads(f.read()) return data[index] Nothing screams “RAT” here, right? But when called like this: test_file("eu", "utf-8", "spellchecker") …it doesn’t return word frequencies. It returns a base64-encoded downloader hidden inside the dictionary entries under the key spellchecker. That downloader then pulls down a Python RAT — turning an innocent spelling helper into code that can: - Execute arbitrary commands remotely
- Read files on disk
- Grab system info or screenshots
- …and generally turn your machine into their machine So yeah… you weren’t fixing typos — you were installing a tiny remote employee with zero onboarding and full permissions. We reported both packages to PyPI, and they’ve now been removed.
(Shoutout to the PyPI team for moving fast.) Checkout the full article here -> https://www.aikido.dev/blog/malicious-pypi-packages-spellcheckpy-and-spellcheckerpy-deliver-python-rat <!-- SC_ON --> submitted by /u/Advocatemack (https://www.reddit.com/user/Advocatemack)
[link] (https://www.aikido.dev/blog/malicious-pypi-packages-spellcheckpy-and-spellcheckerpy-deliver-python-rat) [comments] (https://www.reddit.com/r/programming/comments/1qkwrks/malicious_pypi_packages_spellcheckpy_and/)
Explainability Is a Product Feature
https://www.reddit.com/r/programming/comments/1qkxlmw/explainability_is_a_product_feature/

<!-- SC_OFF -->Admins, support staff, and operations teams are first-class users of your system, yet most systems treat them as afterthoughts. When systems hide their reasoning, these humans absorb the cost. They field angry tickets, craft apologetic responses to frustrated customers, and stay late trying to understand why something happened so they can explain it to someone else. The stress accumulates. Blame spreads. Burnout follows. Poor explainability doesn’t just create technical debt, it creates organizational drag. Every unexplainable behavior becomes a meeting, a Slack thread, an interruption that pulls someone away from actual work to perform forensics on their own system. The system’s opacity becomes everyone’s problem. <!-- SC_ON --> submitted by /u/Unhappy_Concept237 (https://www.reddit.com/user/Unhappy_Concept237)
[link] (https://open.substack.com/pub/hashrocket/p/explainability-is-a-product-feature?utm_campaign=post&utm_medium=email) [comments] (https://www.reddit.com/r/programming/comments/1qkxlmw/explainability_is_a_product_feature/)
Breaking Key-Value Size Limits: Linked List WALs for Atomic Large Writes
https://www.reddit.com/r/programming/comments/1qkz5d0/breaking_keyvalue_size_limits_linked_list_wals/

<!-- SC_OFF -->etcd and Consul enforce small value limits to avoid head-of-line blocking. Large writes can stall replication, heartbeats, and leader elections, so these limits protect cluster liveness. But modern data (AI vectors, massive JSON) doesn't care about limits. At UnisonDB, we are trying to solve this by treating the WAL as a backward-linked graph instead of a flat list. <!-- SC_ON --> submitted by /u/ankur-anand (https://www.reddit.com/user/ankur-anand)
[link] (https://unisondb.io/blog/breaking-kv-size-limits-linked-list-wal/) [comments] (https://www.reddit.com/r/programming/comments/1qkz5d0/breaking_keyvalue_size_limits_linked_list_wals/)
Why Developing For Microsoft SharePoint is a Horrible, Terrible, and Painful Experience
https://www.reddit.com/r/programming/comments/1qljjlx/why_developing_for_microsoft_sharepoint_is_a/

<!-- SC_OFF -->I've written a little article on why I think SharePoint is terrible. Probably could've written more, but I value my sanity. The development experience is painful, performance falls over at numbers a proper database would laugh at, and the architecture feels like it was designed by committee during a fire drill. Writing this one was more therapy than anything else. I recently migrated from SharePoint to something custom. How many of you are still using (or working on SharePoint), and what would you recommend instead? <!-- SC_ON --> submitted by /u/jordansrowles (https://www.reddit.com/user/jordansrowles)
[link] (https://medium.com/@jordansrowles/why-developing-for-microsoft-sharepoint-is-a-horrible-terrible-and-painful-experience-aa1f5d50712c) [comments] (https://www.reddit.com/r/programming/comments/1qljjlx/why_developing_for_microsoft_sharepoint_is_a/)