Untitled topic • Hacker News Board

Re: undefined

#51

Post by anotherlogin448 » Tue, Sep 23, 2025, 5:22 PM UTC

jamesnorden wrote: post #48

remnant24 wrote: post #44

Earlier quoted context omitted.

It's a completely useless observation. Doesn't add anything productive to the topic.

It's not useless, a new account commenting what amounts to "There's nothing wrong, stop looking", multiple times, is the opposite of assuring.

no one said stop looking; simply that OP was wildly misinformed and he proved nothing of any value

Re: undefined

#52

Post by bfLives » Tue, Sep 23, 2025, 7:07 PM UTC

wok4899 wrote: post #47

iogjoertsnbu wrote: post #34

Earlier quoted context omitted.

that's just grep showing you your own grep process lol. you can do ps -ef | grep foobarbaroof and get the same thing...

Damn it!! Yeah, morning bran without coffee! Thank you for pointing it out. My bad.

You can use pgrep to avoid this.

Re: undefined

#53

Post by thephyber » Tue, Sep 23, 2025, 9:01 PM UTC

ponchel wrote: post #26

thephyber wrote: post #18

The article hasn’t proven that the infection is in the GHCR Docker image, let alone the newest version. It only says that they had the image installed, then (unknown time later) noticed the infection. According to some messages on Hotio’s Discord server from 2023-11-25, qBitTorrent moved from fixed admin credentials to randomized at initialization. I think MrHotio’s message about that crypto miner was likely a joke a…

Currently, on my own system, the docker container of qBitTorrent definitely doesn't seem to use more resources than it should.

Unfortunately this doesn’t prove absence of infection.

Cryptominers have become adept at hiding their symptoms when users are looking/interactive.

Just use the best security hygiene — always use the newest version of the app, ensure the admin credentials aren’t low entropy/hard-coded, and hopefully that the admin panel isn’t internet accessible.