Menu

My program behaves like a trojan. Here is what makes it not one (part 2)
📰

My program behaves like a trojan. Here is what makes it not one (part 2)

DEV Community: security·Peter Mamrukov·8 days ago
#5XX0eAi6
#devtosecurity#devto#dev#file#kaspersky
Reading 0:00
15s threshold

In part 1 I told how my npm account got locked, Kaspersky deleted a file from my program as a trojan, and GitHub listed my package as malware. I promised Kaspersky's decision. Here it is, and it isn't the clean ending I wanted.

I build Local Commander, so read everything below as the author's side of the story.

Kaspersky's decision

On November 5th Kaspersky's allowlist team answered about the file I had submitted, JobHost.exe from version 0.3.58: "Sorry, it was a false detection. It was fixed." My application to their Allowlist Program went to their malware experts, which can take 12 to 14 business days.

The next day the detection came back.

The new JobHost.exe, from version 0.3.64, is the version where I had removed the behaviour that looked suspicious. It ran for two days on my own test computer with Kaspersky Endpoint Security. Then the antivirus databases updated on November 6th, and Kaspersky quarantined it while it was running a command I had asked for.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.