crates.io: Malicious crates faster_log and async_println | Rust Blog
https://blog.rust-lang.org/2025/09/24/crates.io-malicious-crates-fasterlog-and-asyncprintln/
https://blog.rust-lang.org/2025/09/24/crates.io-malicious-crates-fasterlog-and-asyncprintln/
7 Comments
Ephera@lemmy.ml · 3 pts · 333d
Damn, expected something like this to happen or, well, be detected after the big NPM attacks.
INeedMana@piefed.zip · 2 pts · 333d
What are the proper crates that the malicious ones were pretending to be? (I'm new to Rust)
fartsparkles@lemmy.world · 4 pts · 333d
Both were impersonating fast_log.
INeedMana@piefed.zip · 1 pts · 333d
Thanks :)
async_println is a part of fast_log?
fartsparkles@lemmy.world · 6 pts · 333d
Both faster_log and async_println were purely malicious packages (not taken over and turned malicious).
I know faster_log is typosquatting / luring fast_log users but I’m not sure about about async_println (which was a clone of the malicious faster_log).
async_std::print is a thing so I guess trying to lure users who search crates before docs :shrug:
nebeker@programming.dev · 2 pts · 333d
I mean, if you want your prints to be asynchronous you’re looking for trouble to begin with.
The previous statement is a joke.
amgdvx@programming.dev · 2 pts · 333d
Seriously more effort and investment should be put into code scanners if we want a bright future to modern software development