everybackdoor

6 ms·

1. 1.▲
   by everybackdoor 2y ago

   This is about NestJS, not NextJS.
2. 2.▲
   by everybackdoor 2y ago

   You can also fire events on pretty much any object, essentially creating a channel where the message bus queue is the vm event queue.
3. 3.▲
   by everybackdoor 2y ago

   In 2024 we have linters and other static analysis tools for catching these kinds of things right in the IDE.
4. 4.▲
   by everybackdoor 2y ago

   And a backdoor in a build tree
5. 5.▲
   by everybackdoor 2y ago

   - They’re saying ” the community wants less boilerplate” - They introduce what is effectively a black-box system - The new system is expected to handle all application state - They try to push it for frontend folks while also remarking tha
6. 6.▲
   by everybackdoor 2y ago

   Look at the newest commits, do you see anything suspicious: https://git.alpinelinux.org/aports/log/main/gettext libunistring could also be affected as that has also been pushed there
7. 7.▲
   by everybackdoor 2y ago

   JiaT75 was also a prolific contributor to xz over the past few years, so your assumptions are generally invalid at this point.
8. 8.▲
   by everybackdoor 2y ago

   Funny you should say that, given they definitely have exploit code in `vcpkg`
9. 9.▲
   by everybackdoor 2y ago

   They may be right: https://git.alpinelinux.org/aports/log/main/gettext Timeline matches and there is a sudden switch of maintainer. And they add dependency to xz!