Currently contains a discord token scraper, DO NOT INSTALL

[Happyrobot33]

Recently just had a friend get their discord taken over after installing this addon. Its unclear if this repository itself is compromised, or if one of the dependencies is, but either way, this repo should be avoided for now

[Rycia]

Can confirm this. Lags when installing dependencies in the addon window in blender itself. Lags a moment and then the second it installed, Discord started mass dm'ing people.

[M3KAI5ER44]

I personally don't see any signs in any recent commits that would suggest that the addon itself is causing it, perhaps a dependency done by the pip importer was compromised??

edit: i didn't do a comprehensive read through, but I can confirm my account is in good standing with the versions of packages I have installed on this version of the addon from around the time the release was made.

e2: unless the pip endpoints were hyjacked themselves, i don't see how that could be it.

the lag that happens when installing dependencies should be normal as from my experience it pauses blenders execution when doing so.
it would be excellent if someone can run this through a VM and wireshark to pinpoint where this is happening as im away rn.

[jlai]

Well I'm not keen on testing this out myself, but the pip packages it installs are locked to a version if I'm reading that code correctly

The packages it installs are SpoutGL==0.1.0 (Windows-only), syphon-python==0.1.0 (Mac only), and cyndilib==0.0.5.

SpoutGL 0.1.0 was released in August 2024 (I wrote it). It has no dependencies.
cyndilib 0.0.5 was released in January 2025. It has only one dependency, numpy, which is widely used.

C:\blender-5.0.1-stable.a3db93c5b259\5.0\python\bin>python -m pip install --ignore-installed --dry-run cyndilib==0.0.5
Collecting cyndilib==0.0.5
  Downloading cyndilib-0.0.5-cp311-cp311-win_amd64.whl.metadata (6.4 kB)
Collecting numpy (from cyndilib==0.0.5)
  Using cached numpy-2.4.1-cp311-cp311-win_amd64.whl.metadata (6.6 kB)
Downloading cyndilib-0.0.5-cp311-cp311-win_amd64.whl (13.2 MB)
   ---------------------------------------- 13.2/13.2 MB 3.6 MB/s eta 0:00:00
Using cached numpy-2.4.1-cp311-cp311-win_amd64.whl (12.6 MB)
Would install cyndilib-0.0.5 numpy-2.4.1

Didn't check syphon-python since I don't have a Mac, but it was released in 2023 and PyPi metadata says:

curl -L "https://pypi.org/pypi/syphon-python/json" | jq '.info.requires_dist'
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 15825  100 15825    0     0   282k      0 --:--:-- --:--:-- --:--:--  286k
[
  "pyobjc-core ~=10.1",
  "pyobjc-framework-metal ~=10.1",
  "pyobjc-framework-cocoa ~=10.1",
  "pyopengl ~=3.1.7"
]

[M3KAI5ER44]

I honestly don't see how there is any correlation then.
The dep packages in question haven't been touched in a long time and have been notably safe for use ever since.
and no recent commit to this repo seems to have any code that could possibly do much more than what this repo says it does (and I can vouch seeing as I've been safe with it installed since the day of the latest release and have had nothing happen with discord or any of my other accounts)

---

In my personal opinion unless there is any proper evidence other than "thing felt weird and then something happened", I don't see how this repo or any of it's dependencies could have anything to do with discord token theft.
This in mind, opening an issue to say that there is a discord token scraper can be done with good intent, like of course if there really was/is one. But in this case, if it's really just a boy-who-cried-wolf situation, then it's only causing a stir, making people fear something that is totally harmless (which just happens sometimes, so don't worry too much).

Nonetheless, I encourage anyone that is confident that there really is a scraper somewhere along the line of execution to take a closer look to see if there's anything actually going on.

If I'll be honest I'm a bit all talk on the sandbox, cause if there really-really IS something in there right now (somehow post-me installing it a couple weeks ago) I wouldn't want to risk it being on my network, as I currently don't exactly have a great way to get internet isolated to a VM due to my "favorite local ISP" being annoying as hell :P.

[Rycia]

Heyo!

HappyRobot33 was talking to me right as this happened. He posted this on my behalf while the chaos ensued and I didn't have time to react, so I made a short post early on. I secured myself now so I can actually make a post about what happened.

I was literally minding my own business working in Blender talking to him about this repo and the second I clicked on the dependencies from inside the Blender add-on window, I had a slight freeze and then my discord starting going erratic at the exact same time. I don't know if it was coincidence or a mix of factors. I picked up on a lot of information after the incident in various forms of logs and research/recon. I didn't pick up too much information because the goal was to secure myself, then figure out what happened after, and I did a full wipe on my C: drive from USB to be safe, after rebooting with disconnected Ethernet to very briefly look at some settings and wipe. I decided to secure now, investigate later.

1. I have a Ubiquiti Router, which provides extremely verbose logging, I looked at that and I was getting port scanned constantly starting from the night before. After the incident, I blocked HUNDREDS of IP addresses that were consistently port scanning and getting blocked. One of the packets successfully found one of my open ports the night before.
2. One of the logs was my PC sending info to a domain under unchewq.cyou which is registered commonly under a infostealer called Lumma Stealer, which was blocked, but confirmed the infection was Lumma Stealer.
3. Hundreds of alerts overnight into the day of of port scanners, possibly a botnet, trying to find open ports, now that it found one and got greedy, I have to wait for a WAN IPV4 address change from my ISP now while I have any previously port forwarded port disabled.
4. My windows install of windows 11 was old and past due on a refresh, so RCE vulnerabilities likely existed on my system. I have VoiceMeeter installed, and, in fact, VoiceMeeter drivers prevent windows from updating because Microsoft is petty, so I wasn't using the latest version of Windows 11 either.
5. I found no source of files, but it absolutely was executing code using elevated Powershell, which then somehow made tasks in Task Scheduler that ran every 10 minutes for 1 minute; at this point I was disconnected from the internet and letting it run while I snooped around for a moment before quickly wiping.
6. Windows Defender kept catching a system32 file that every few seconds was getting injected with code, then removed, then injected again, and just looped, so it was something deep rooted that Defender couldn't figure out. This was immediately after the initial attack on my Discord token.
7. It is indeed possible as M3KAI5ER44 said, that my pip installation could of been injected or somehow altered where any time I would install a package, a script would of ran instead which could of triggered the Discord behavior. If an attacker was already in my system, they could of known I use Python and decided to inject it into Blender right before I was going to open it with remote access, with the goal of gaining elevated privileges to do damage.
8. It's also possible that an attacker found an open port and ran with it and ran RCE exploits on my system at a really coincidental time, and nothing to do with Blender.

In general, it looks like its likely not this repo, but an astronomical coincidence. I would still do some sort of forensics on this repo and its dependencies just to be safe. In the meantime, I'll refrain from the repo and monitor my network to see if anything else goes on for the next few days. I was going to try running this in a VM, but VM's don't support the OpenGL version Blender requires as of 5.0, so I hadn't had a chance to test it. I tested other things I've recently ran and done as a simulation and everything I did the last few days leading up to this, even manually diving in with SysInternals' Process Explorer, with absolutely nothing suspicious, so it leads more into the probability of just an unfortunate and very unlucky cyberattack.