[Pajeeter]

1. use tools like nmap to scan for open ports on the gitLab instance look for port 80/443 for web 22 for SSH.

2. find a vulnerability maybe it's an outdated gitLab version with known cves or a weak admin password. 

3. once you're in look for the CI/CD configuration files. They're usually in .gitlab-ci.yml in project repos.

4. modify the YAML files add commands to the build process maybe a backdoor or some data exfiltration.

5. force a new build to run your injected code.

6. delete the logs bro for the sake of your mother.

[udy4t]

How successful is this method? I kind of feel like it would very easy to detect by the developer pretty quick

This forum account is currently banned. Ban Length: Permanent (N/A Remaining)
Ban Reason: Spamming | http://c66go4clkqodr7tdjfu76jztjs7w7d3fajdeypxn73v4ju3dt7g5yyyd.onion/Forum-Ban-Appeals if you feel this is incorrect.

[dvx]

Thanks for this elite guide. Will now target NASA by using these HTML injection methods.

[Pajeeter]

Thanks for this elite guide. Will now target NASA by using these HTML injection methods.

saar it doesnt work like dis saar