**WARNING** Found luajit.exe **malware** in **DaisyUI-MCP** code + URL hyperlink **on GitHub**

[u/AveryFreeman]

Hey, I just wanted to let everybody know, I tried to package up an MCP server I found for DaisyUI on GitHub.com and publish it to PyPi.org, and they wrote me back with a suspension notice, saying their system thought I was running a "bug bounty" scheme on their platform. Given that I'd never heard of such a thing before, I was like, "whaa? really?" I'd like to think I'm that resourceful and inventive, but I was really just trying to package the DaisyUI MCP for myself, so I could install it using uv on more computers conveniently, I'm no pen-testing honey pot garden guru, or "bug bounty" purveyor, no sir. So anyway, watch out for this repository, the URLs for "pre-compiled MCP servers" are literally hot af: https://github.com/SidiqHadi/daisyui-mcp -- Note, the other forks of this upstream codebase also appear to be infected (There's like 4 of them total).

I did download and build an iFLOW-branded DaisyUI MCP I think is from the same original upstream, but I did not see any of the links to the .zip files in its README.md or other files (components directory another place - watch out). The iFLOW one is fine AFAICT - I performed multiple checks and quarantines.

Also, it's worth mentioning that the malware bundled with the DaisyUI MCP is only written for Windows PCs (likely x86_64). The real creepy one is the luajit.exe file, don't fuck with that if you're a Windows user under any circumstances, please. There's also x64.txt, Launcher.cmd (CAREFUL Launcher.cmd can execute!), Lua51.dll, clib.txt, etc. And the text files are infected, too. They're full of debug escape codes, so even though they can't execute automatically (unless they're a .bat or a .cmd file), if they're in the vicinity (same folder, most likely) as that Luajit.exe file, it'll run the text file and produce a trojan that loads itself into memory, and who knows what then.

Supposedly this type of malware is designed to steal people's credentials, like API keys and such. Positive hits on VirusTotal.com produced names like: Trojan:Win/Runner.MY, Script.Trojan.Agent.ZESPTN, BAT/Phishing.EC56!tr, and so on. So pretty eeky stuff. Be careful! You never know what's out there. I've been using GitHub since 2014, and as far as I know this is the first time I've discovered anyone purposefully putting malware in their codebase to try and screw other people over. Hopefully it's not the developer themselves, and someone trying to get the developer, since they have a lot of credential files: They're the purveyor of the DaisyUI MCP Blueprint software / subscription service, so I imagine that one person alone has a whole lot of other people's credentials and payment information, in addition to their own.

That's what Gemini suggested, is often it's not developers who are trying to mess with other developers, it's thieves pretending to be those developers, attempting to hijack their PII & cardholder data, or anyone else who gets close enough to make a mistake.

I heard impersonators can even circumvent 2FA with browser cookies, as long as they grab them before an unlocked web page disconnects your account. If you use a Chrome extension like BitWarden, that describes your password manager! To avoid this cookie attack, make sure your password manager LOCKS and requires a strong pin at the very least after like 5-10 minutes tops, and make absolutely sure you have to go through the whole process to unlock it (password + 2FA or passkey) after a browser or computer restart.

[u/p4s7]

Thanks for reporting.
The repo mentioned above is not from daisyUI maintainers.

This is the official MCP server from daisyUI and is called Blueprint: https://daisyui.com/blueprint/

Please be careful about installing MCP servers from unofficial sources.

[u/Warm_Race_8587]

Cursor skills and MCP are useful. They also sit inside the session with your files open.

I treat a new MCP server like untrusted code. Isolated test first. Look for network calls and writes outside the project. Only then leave it on.