# Malicious code in pyTorch

**URL:** <https://discourse.slicer.org/t/malicious-code-in-pytorch/27021>\
**Category:** Support\
**Created:** [January 4, 2023, 12:45am UTC](https://discourse.slicer.org/t/malicious-code-in-pytorch/27021 "2023-01-04T00:45:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/83011_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)\
**Post date:** [January 4, 2023, 12:45am UTC](https://discourse.slicer.org/t/malicious-code-in-pytorch/27021/1 "2023-01-04T00:45:04Z")

</div>

Should we be concerned about this?

> If you installed PyTorch-nightly on Linux via pip between December 25, 2022 and December 30, 2022, please uninstall it and torchtriton immediately, and use the latest nightly binaries (newer than Dec 30th 2022).

`https://pytorch.org/blog/compromised-nightly-dependency/`

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [January 4, 2023, 12:51am UTC](https://discourse.slicer.org/t/malicious-code-in-pytorch/27021/2 "2023-01-04T00:51:17Z")

</div>

Thanks for posting, that’s a scary precedent.

Maybe someone can confirm, but I believe our installers would only have provided the stable releases and not the nightlies for PyTorch.