![Malicious GO package Malicious GO package](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgoMmlQauu6kMFdILGbz2N874lk0gOm_-C3D7Uxz8n4vW56xHolsFgQUI2gHZowL5EagqWrhu1n1z5lcdcPzIjUBOWl_RRj3YPjiTsFWrPFpxBdkn_LPZb-pks-oXh4ArfArMS-5ZTZx2HVy4TELuhvkGfNI1zY06rTzdsS83MiPtBmTJ2sM-oxZq9PNhlj/s728-rw-e365/go.png)
Cyber Security researchers have paid attention to software supply chain attacks targeting GO ecosystem, including malicious packages that can give hostile remote access to infection systems.
The package named gitHub.com/boltdb-go/bolt is a type cut of the legal boltdb database module (github.com/boltdb/bolt) for each socket. The malicious version (1.3.1) was released on GitHub in November 2021, and was then cached indefinitely by the GO module mirror service.
“Once installed, the background package will give a remote access of a threat actor to the infected system so that any command can be executed,” said the security researcher, Cyril Boychenko, said in an analysis. 。
According to Socket, this development marks one of the first instances of the malicious actor who abuse the indefinite cache of the Go Module Mirror module, deceives users and download the package. He said he was doing it. Later, it is said that the attacker changed the Git tag in the source repository to redirect them to a benign version.
![Cyber security](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhc0hgq4JZKi-PJjUZ4kdb5ficmXr3IPOg6noFF558_qZ-gXm7vb0OzXU0NzsPAxaqca2tLI5j8NgJW731W0_CuPrUerOmSrZSt4IeANQp6VAQsIAQUzv6aJsxBD6poxHfELq0bcbeevSVy5AyOb9ganALMoA140nZoLOtSb0ck2AZ5rZgb9mWDEyVsbvqK/s728-rw-e100/saas-security-v1-d.png)
This deceptive approach guarantees that manual audit of GitHub repository does not reveal malicious content, but cash mechanisms do not doubt developers who do not doubt that they use GO CLI to install the package. It means that we continued to download the variant.
“If the module version is cached, you can access it through the Go module proxy,” says Boychenko. “This design gives a legal use case, but the threat actor used it to permanently distribute malicious code, despite subsequent changes to a repository.”
![Malicious GO package Malicious GO package](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjNRUIpmn_AAaEaE-Hvxn_u0r0MlthKYheFpsd-VLFOZl8Bpf6CWoVP_PLCmrw3FmhQBrA-CcDxwFxWB63_WoQkfoBeDq3UOFE8d0uGGxzTl9RWfcIPVFKFHlKa5eH1vvsM2Cro3-UCb7AGCjtV4jGXdctqTtaQhVfYQ71stRhy9VOl3yFqr24hDjKQWJ1q/s728-rw-e365/git.png)
“In the immutable modules that provide both security profits and potential abuse vectors, developers and security teams need to monitor attacks to avoid detection using the cached module version.”
Development occurred when Cycode has detailed the three malicious NPM packages (Serv Static Corel, OpenSSL-NODE, and NEXT-Refresh-Token) in detail.[.]60 “) The infected host.
Source link