A sneaky demonstration of the dangers of curl | bash - k3can blog
blog.k3can.us

I set up a quick demonstration to show risks of curl|bash and how a bad-actor could potentially hide a malicious script that appears safe.

It’s nothing new or groundbreaking, but I figure it never hurts to have another reminder.

  • ShortN0te@lemmy.mlEnglish
    1·
    3 hours ago

    No you cannot, the pub key either needs to be present on the updater or uses infrastructure that is not owned by you. Usually how most software suppliers are doing it the public key is supplied within the updater.

    • xylogx@lemmy.worldEnglish
      1·
      2 hours ago

      Not sure how else to explain this. Look at the CISA bulletin on Shai-Hulud the attacker published valid and signed binaries that were installed by hundreds of users.

      "CISA is releasing this Alert to provide guidance in response to a widespread software supply chain compromise involving the world’s largest JavaScript registry, npmjs.com. A self-replicating worm—publicly known as “Shai-Hulud”—has compromised over 500 packages.[i]

      After gaining initial access, the malicious cyber actor deployed malware that scanned the environment for sensitive credentials. The cyber actor then targeted GitHub Personal Access Tokens (PATs) and application programming interface (API) keys for cloud services, including Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure.[ii]

      The malware then:

      • Exfiltrated the harvested credentials to an endpoint controlled by the actor.
      • Uploaded the credentials to a public repository named Shai-Hulud via the GitHub/user/repos API.
      • Leveraged an automated process to rapidly spread by authenticating to the npm registry as the compromised developer, injecting code into other packages, and publishing compromised versions to the registry.[iii]"
      • ShortN0te@lemmy.mlEnglish
        1·
        1 hour ago

        After gaining initial access, the malicious cyber actor deployed malware that scanned the environment for sensitive credentials.

        So as I said, the keys got compromised. Thats what i said in the second post.

        • xylogx@lemmy.worldEnglish
          1·
          7 minutes ago

          What you said is the key infra needs to get compromise. I do not need to own the PKI that issued the certs, I just need the private key of the signer. And again, this is something that happens. A lot. A software publisher gets owned, then their account is used to distribute malware.