Man
Professional
- Messages
- 3,038
- Reaction score
- 561
- Points
- 113
Start
In this guide I will tell you in detail how to correctly upload Github to stealer from A to Z.
The story of my path:
I will say right away. Github is not fucked!and fat logs can be safely looted. My profits were quite large. I tried to work out all the requests that I could. But often I missed exchanges/banks. But even from the same carts and discord tokens, $ 100 per month came out.
From the very beginning, I did not follow in the footsteps of others and did not copy everything 1 to 1. I immediately tried a lot of options and patterns that helped me in the flood and with the help of all this I was able to pour ~2.6k logs in several months on a full passive
(The statistics are not complete, since there were different updates in the team due to which ~300 logs disappeared in my statistics).
On the cold ones there was basically nothing, a maximum of 150-200$ looted from them. Everything else is processing requests
Proof
The first days of the bay:
Initially, when I just started studying the fill through Github:
The team gave free cheating and cookies, which really helped and from scratch I was able to break into this area. The most important thing for me was - cookies. At first, cheating may have helped to be in the top among tags, such as crack adobe photoshop, etc. but after a week or two, absolutely everyone started to fill these requests. :ehh: In the first 2-3 days of filling, I was able to make 100 logs per day with cheating on a Photoshop crack, I was very happy and then I got my first big profit.
After that, I began to study the fill with the help of autoregs and as for me, this was the best way to fill, unlike cookies, but later the shop where I bought cookies - I could no longer register them, so I switched to cookies that the team gave me. I filled in cracks of popular games and programs. Many repositories climbed to the top of the search engine for me - roblox executor / cupcut pro / genshin impact mod menu / valorant aimbot / hwid spoofer valorant / fortnite wallhack / 4k video downloader, etc. Logs did not appear immediately, it depends on the popularity of the request. Logs could start appearing after 1-3 days, or after 2 weeks, and at the same time stay in the top of the search engine for a long time, until your account is deleted.
The essence of creating themes was to literally make every cheat for a game or program - like: valorant wallhack / valorant aimbot / valorant skinchanger / valorant cheat, etc. And with the help of ChatGPT, you can create repository designs in a few seconds and without any effort. Your main task is to write well-written tags, due to which your repositories would appear in the top of the search engine and you would loot the logs. I was partly lazy, but I still uploaded and received my logs on a full passive. When the star boosting broke in the team, I started looking for a solution to this problem.
And at the moment when GitHub was twisting the stars on the repository, as a result, 0 stars remained on the repository and I started getting logs. At first, I did not understand what the joke was, but then I began to analyze this topic in more detail and in the future I always uploaded repositories without stars. 90% of the logs that I received were without boosting the stars on the repositories. I uploaded 1 repository per 1 cookie, you can upload several if you have few cookies, but if 1 repository is banned, the entire account flies off.
That's the story. Let's start the guide!
Accounts
There are two types of accounts:
Autoreg - It is very difficult to create a high-quality GitHub account manually, since there will often be a Shadowban. Even if you use high-quality proxies and antic, this will not guarantee the creation of an account without shadows. Such accounts can be created, but the chance is small. If you manage to create autoregs without a shadowban - be sure to use them, since using them you have only advantages. You will always have access to the account to replace the build or link (I will not teach you how to create accounts. If you find a shop where autoregs without shadows are sold for up to $0.5, this will already be a success!)
Cookies - A good option if you want to upload repositories with banned tags. Basically, you will use the upload via cookies. Uploading with banned tags does not always work and personally I was able to upload only via auto-upload and this is not often successful. You will only kill your cookies, so it is better to upload without risks.
The cookie itself lives up to 1-2 days. During the upload, they fly away in very rare cases.
Where can I get cookies? - You can buy them, check different clouds with logs with Checker, get them from your own logs, and also through the mail cookie, renew the GitHub account and change the data (the only downside is that the mail cookie itself can die).
Pros - you can upload by banned tags (alas, but this will not give any profit and the upload happens in rare cases, besides, the ban comes quickly)
Cons - the cookie dies after a while / You will only have 1 time to download the file / link
How to create a repository
Where to create
How to create correctly
Be sure to check the README box! Without it, you won't be able to submit your repository.
How to start designing repositories
When creating a repository, do not forget to check the name for a ban via https://github.com/topics/ name
The name must be without spaces, you need to use a minus instead of all spaces
Example: fortnite-hack / fortnite-aimbot-menu - if the error is 404 - Do not use!
Since the name can also destroy the account.
Repository design
I initially didn't want to follow the basic manual like everyone else. That's why I worked on the design of my repository so that it would look aesthetically pleasing. It doesn't really affect anything, but it's much better than
just text or a picture.
My version, which I came up with initially
Option with picture
Personally, I didn't like the picture and I didn't even use it, because it looks stupid overall.
Repository Preview
It is also quite important to have a picture on your repository, as it stands out very much against the background of different repositories. Often when you write unique tags, there will be no competitors, but in rare cases you may come across the same tags.
How a repository with an image is highlighted
I had a whole pack of previews for different topics
If you have no experience, you just need to ask the designer to make a preview and give you the source files. In my case, the source file and preview were received on green in "Free graphics".
Even without great Photoshop skills, I simply changed the text/text colors/game icon/lighting. The most expensive thing is finding a good quality game icon without a background. But when you get the hang of it, you can make ~10 previews per hour. (I won't send you the source file, be unique).
Text design
Use beautifully formatted text for your repository. You can find
all text tags for formatting HERE.
Use bold text, make the main keywords large, etc. (an example would be the very first picture of how I formatted my repository).
You only need to make a large and beautifully formatted text once, and to rework it for different topics, use ChatGPT. Give it a prompt and send your finished version of the text. Sometimes you need to adjust it to bring it to perfection. Example of a prompt: I have text and I need to make it in the same style, just change the entire main text to the topic I want and do it in code format. It will rework all the words and even tags in the repository itself to suit your topic and you can copy the entire text in 1 click. All you have to do is manually upload pictures/links via GitHub.
How it should look
You can upload images by simply copying them and CTRL + V
It is uploaded to the GitHub hosting itself. In case of an account ban, all images that were uploaded to the GitHub hosting are deleted
Important! Do not copy the link to the image from other repositories, since when the account is blocked, the image will simply disappear and there will be just clickable text
I can't say anything about tags in the README, since it is unlikely to change anything. Basically, your repository rises to the top of the search engine only due to tags and partly because of
the name
How to make a picture clickable
Initially, we upload the image by copying it and CTRL + V. After uploading to the GitHub hosting, it will be in this format:
1:
You need to put square brackets [ ]
at the beginning and end. Then at the end, enter the link to your file in brackets ( ).
This is how it should look like for you:
2:
Final version
How to upload a file
I have tried many budget ways to upload a file and not lose logs in case of a dead cookie.
FO - A good option, but often FO detects that your file contains a virus and completely blocks the file.
Shorteners - often also ban your link / account for suspicious files.
FTP - If you upload to FTP, they will hang sooner or later CT and FTP do not live forever.
Discord direct link - As before, you will not be able to use this method, since Discord will sooner or later change the link, and the old one will be unavailable.
The best option is to upload the file along with the repository.
IMPORTANT! Do not use links to the file from other uploaded github accounts, since if the account dies, the link will also die. Even if you have a new reg without shadows, where you simply upload a file and post a link from other accounts, the account will disappear along with the link.
You can also use your own loader and similar hat, no one forbids.
Guide on how to upload a file to github.
Go to Releases
File loading
You can simply copy the link and post it in README so that the mammoth goes to the download page, or you can post a direct link,
How to get a direct link
Bans and Shadows
All bans look the same, just error 404. In case of an account ban, you will be simply kicked out of the account and this will be a 100% ban.
And also when your repository is not displayed from any other device and it says error 404 - this is a shadow ban of the account. In fact, the account is alive, but your profile and repository are not visible to anyone and it says "error 404" - such accounts are sent to the trash.
What an account ban looks like
They will ban mainly for your tags and in very rare cases a ban can come because of banwords in the repository itself (it is enough to change the text a little through gpt).
Repositories cannot live forever. It already depends on your topic, and also your tags on the repositories can start to be banned. They can ban everything at once and then delete the account, or they can only ban a few and slowly ban the rest. This will not affect your repository in any way. But when all tags are banned - your account will be banned in the near future
(Do not try to change tags on a live repository, you will only increase the chance of a ban, and you can also kill your cookie. Leave everything as is, wait until your repository flies into the top of the search engine).
How to check tags for a ban
https://github.com/topics/ tag-tag-tag
What does a tag ban look like?
What a non-banned tag looks like
In very rare cases, it happens that it shows that the tag is not banned, but still deletes the account.
Correct spelling of tags
The most important part, on which your repository's inclusion in the Google / Bing search engine and others depends.
Previously, I already had experience with creating tags for YouTube, since I was previously a trafficker, so I had an understanding of which tags are best to use.
Remember that tags = keywords that promote your repository.
To select tags, I used the site - https://keywordtool.io/
Website
In general, it doesn't matter from which source to take tags, they will be the same everywhere. I always used the free version of this service
Write 1 keyword on your topic that you want to do. You can also sort through this site and write "download cupcut pro crack"
You need to choose tags that look like full-fledged keywords. Let's consider which ones are suitable and which are not
Tags that fit
Also, when there are very few tags, go through them in this format:
capcut pro crack pc / capcut pro crack download for pc / free download capcut pro / download capcut pro crack
Add the words free / download / crack / cracked / for pc / pc crack etc.
at the beginning and at the end. For games, also use the words download / free / cheat(s) / hack(s) / wallhack(s) / aimbot(s) etc.
Also, when you immediately select a tag, immediately check it for a ban using https://github.com/topics/tag.
In the bans and shadows section, I showed what a tag ban looks like.
What to do if your request is unique and there are almost no tags?
Write a request ChatGPT - "Write popular tags on the topic of genshin gayporno crack"
It will give you basic tags, you also check them for a ban and remove garbage tags that are not associated with your topic
Examples of tags that I wrote on popular topics and on NN, which had very few tags
Example
You just need to understand the essence of how to write tags correctly. In an hour, with a trained hand, I was able to make 5-8 packs with tags (1 pack - 20 tags).
When you select tags, be sure to check them on your autoreg, just register it yourself and it doesn't matter whether there is a shadow or not.
Where to publish tags
Publish 1 tag at a time and wait 10-20 seconds - if it kicks you out of your account = tag ban. Don't forget that even if you checked the tag for a ban and it showed you that it is not banned - this does not guarantee that it is not banned, such cases happen very rarely.
My principle for searching and testing tags was as follows:
I search for a tag on the site - I check for a ban (if not banned) - I publish a tag - I search for a new tag at this time, so as not to wait stupidly - I refresh the page and see - banned or not.
You can write your tags in the comments under hide, I can give advice.
Conclusion
Remember that you won't make a mountain of logs right away, you need patience and wait until your topic gets to the top and the logs start pouring in.
If you are very motivated in this, then create more topics and upload them. When you have 300-500 repositories and 10-20-30 of which are repositories in the top - you can easily bring 50-100+ logs every day. Check all your topics 5-7 days after uploading, if the repository is banned - check all the tags - change the banned ones and re-upload.
I can only wish you good luck!
I leave you a link to the project in figma. Where I looked for different icons from programs and games. Figma is very convenient and simple in this regard, you can figure it out even without any skills.
Bonus
https://www.figma.com/design/3nhjN1o7fut8XSzL6qOJxx/Untitled?node-id=0-1&t=yGejQbvKDWTgsXaZ-1
In this guide I will tell you in detail how to correctly upload Github to stealer from A to Z.
The story of my path:
I will say right away. Github is not fucked!and fat logs can be safely looted. My profits were quite large. I tried to work out all the requests that I could. But often I missed exchanges/banks. But even from the same carts and discord tokens, $ 100 per month came out.
From the very beginning, I did not follow in the footsteps of others and did not copy everything 1 to 1. I immediately tried a lot of options and patterns that helped me in the flood and with the help of all this I was able to pour ~2.6k logs in several months on a full passive
(The statistics are not complete, since there were different updates in the team due to which ~300 logs disappeared in my statistics).
On the cold ones there was basically nothing, a maximum of 150-200$ looted from them. Everything else is processing requests
Proof
The first days of the bay:
Initially, when I just started studying the fill through Github:
The team gave free cheating and cookies, which really helped and from scratch I was able to break into this area. The most important thing for me was - cookies. At first, cheating may have helped to be in the top among tags, such as crack adobe photoshop, etc. but after a week or two, absolutely everyone started to fill these requests. :ehh: In the first 2-3 days of filling, I was able to make 100 logs per day with cheating on a Photoshop crack, I was very happy and then I got my first big profit.
After that, I began to study the fill with the help of autoregs and as for me, this was the best way to fill, unlike cookies, but later the shop where I bought cookies - I could no longer register them, so I switched to cookies that the team gave me. I filled in cracks of popular games and programs. Many repositories climbed to the top of the search engine for me - roblox executor / cupcut pro / genshin impact mod menu / valorant aimbot / hwid spoofer valorant / fortnite wallhack / 4k video downloader, etc. Logs did not appear immediately, it depends on the popularity of the request. Logs could start appearing after 1-3 days, or after 2 weeks, and at the same time stay in the top of the search engine for a long time, until your account is deleted.
The essence of creating themes was to literally make every cheat for a game or program - like: valorant wallhack / valorant aimbot / valorant skinchanger / valorant cheat, etc. And with the help of ChatGPT, you can create repository designs in a few seconds and without any effort. Your main task is to write well-written tags, due to which your repositories would appear in the top of the search engine and you would loot the logs. I was partly lazy, but I still uploaded and received my logs on a full passive. When the star boosting broke in the team, I started looking for a solution to this problem.
And at the moment when GitHub was twisting the stars on the repository, as a result, 0 stars remained on the repository and I started getting logs. At first, I did not understand what the joke was, but then I began to analyze this topic in more detail and in the future I always uploaded repositories without stars. 90% of the logs that I received were without boosting the stars on the repositories. I uploaded 1 repository per 1 cookie, you can upload several if you have few cookies, but if 1 repository is banned, the entire account flies off.
That's the story. Let's start the guide!
Accounts
There are two types of accounts:
Autoreg - It is very difficult to create a high-quality GitHub account manually, since there will often be a Shadowban. Even if you use high-quality proxies and antic, this will not guarantee the creation of an account without shadows. Such accounts can be created, but the chance is small. If you manage to create autoregs without a shadowban - be sure to use them, since using them you have only advantages. You will always have access to the account to replace the build or link (I will not teach you how to create accounts. If you find a shop where autoregs without shadows are sold for up to $0.5, this will already be a success!)
Cookies - A good option if you want to upload repositories with banned tags. Basically, you will use the upload via cookies. Uploading with banned tags does not always work and personally I was able to upload only via auto-upload and this is not often successful. You will only kill your cookies, so it is better to upload without risks.
The cookie itself lives up to 1-2 days. During the upload, they fly away in very rare cases.
Where can I get cookies? - You can buy them, check different clouds with logs with Checker, get them from your own logs, and also through the mail cookie, renew the GitHub account and change the data (the only downside is that the mail cookie itself can die).
Pros - you can upload by banned tags (alas, but this will not give any profit and the upload happens in rare cases, besides, the ban comes quickly)
Cons - the cookie dies after a while / You will only have 1 time to download the file / link
How to create a repository
Where to create
How to create correctly
Be sure to check the README box! Without it, you won't be able to submit your repository.
How to start designing repositories
When creating a repository, do not forget to check the name for a ban via https://github.com/topics/ name
The name must be without spaces, you need to use a minus instead of all spaces
Example: fortnite-hack / fortnite-aimbot-menu - if the error is 404 - Do not use!
Since the name can also destroy the account.
Repository design
I initially didn't want to follow the basic manual like everyone else. That's why I worked on the design of my repository so that it would look aesthetically pleasing. It doesn't really affect anything, but it's much better than
just text or a picture.
My version, which I came up with initially
Option with picture
Personally, I didn't like the picture and I didn't even use it, because it looks stupid overall.
Repository Preview
It is also quite important to have a picture on your repository, as it stands out very much against the background of different repositories. Often when you write unique tags, there will be no competitors, but in rare cases you may come across the same tags.
How a repository with an image is highlighted
I had a whole pack of previews for different topics
If you have no experience, you just need to ask the designer to make a preview and give you the source files. In my case, the source file and preview were received on green in "Free graphics".
Even without great Photoshop skills, I simply changed the text/text colors/game icon/lighting. The most expensive thing is finding a good quality game icon without a background. But when you get the hang of it, you can make ~10 previews per hour. (I won't send you the source file, be unique).
Text design
Use beautifully formatted text for your repository. You can find
all text tags for formatting HERE.
Use bold text, make the main keywords large, etc. (an example would be the very first picture of how I formatted my repository).
You only need to make a large and beautifully formatted text once, and to rework it for different topics, use ChatGPT. Give it a prompt and send your finished version of the text. Sometimes you need to adjust it to bring it to perfection. Example of a prompt: I have text and I need to make it in the same style, just change the entire main text to the topic I want and do it in code format. It will rework all the words and even tags in the repository itself to suit your topic and you can copy the entire text in 1 click. All you have to do is manually upload pictures/links via GitHub.
How it should look
You can upload images by simply copying them and CTRL + V
It is uploaded to the GitHub hosting itself. In case of an account ban, all images that were uploaded to the GitHub hosting are deleted
Important! Do not copy the link to the image from other repositories, since when the account is blocked, the image will simply disappear and there will be just clickable text
I can't say anything about tags in the README, since it is unlikely to change anything. Basically, your repository rises to the top of the search engine only due to tags and partly because of
the name
How to make a picture clickable
Initially, we upload the image by copying it and CTRL + V. After uploading to the GitHub hosting, it will be in this format:
1:
You need to put square brackets [ ]
at the beginning and end. Then at the end, enter the link to your file in brackets ( ).
This is how it should look like for you:
2:
Final version
How to upload a file
I have tried many budget ways to upload a file and not lose logs in case of a dead cookie.
FO - A good option, but often FO detects that your file contains a virus and completely blocks the file.
Shorteners - often also ban your link / account for suspicious files.
FTP - If you upload to FTP, they will hang sooner or later CT and FTP do not live forever.
Discord direct link - As before, you will not be able to use this method, since Discord will sooner or later change the link, and the old one will be unavailable.
The best option is to upload the file along with the repository.
IMPORTANT! Do not use links to the file from other uploaded github accounts, since if the account dies, the link will also die. Even if you have a new reg without shadows, where you simply upload a file and post a link from other accounts, the account will disappear along with the link.
You can also use your own loader and similar hat, no one forbids.
Guide on how to upload a file to github.
Go to Releases
File loading
You can simply copy the link and post it in README so that the mammoth goes to the download page, or you can post a direct link,
How to get a direct link
Bans and Shadows
All bans look the same, just error 404. In case of an account ban, you will be simply kicked out of the account and this will be a 100% ban.
And also when your repository is not displayed from any other device and it says error 404 - this is a shadow ban of the account. In fact, the account is alive, but your profile and repository are not visible to anyone and it says "error 404" - such accounts are sent to the trash.
What an account ban looks like
They will ban mainly for your tags and in very rare cases a ban can come because of banwords in the repository itself (it is enough to change the text a little through gpt).
Repositories cannot live forever. It already depends on your topic, and also your tags on the repositories can start to be banned. They can ban everything at once and then delete the account, or they can only ban a few and slowly ban the rest. This will not affect your repository in any way. But when all tags are banned - your account will be banned in the near future
(Do not try to change tags on a live repository, you will only increase the chance of a ban, and you can also kill your cookie. Leave everything as is, wait until your repository flies into the top of the search engine).
How to check tags for a ban
https://github.com/topics/ tag-tag-tag
What does a tag ban look like?
What a non-banned tag looks like
In very rare cases, it happens that it shows that the tag is not banned, but still deletes the account.
Correct spelling of tags
The most important part, on which your repository's inclusion in the Google / Bing search engine and others depends.
Previously, I already had experience with creating tags for YouTube, since I was previously a trafficker, so I had an understanding of which tags are best to use.
Remember that tags = keywords that promote your repository.
To select tags, I used the site - https://keywordtool.io/
Website
In general, it doesn't matter from which source to take tags, they will be the same everywhere. I always used the free version of this service
Write 1 keyword on your topic that you want to do. You can also sort through this site and write "download cupcut pro crack"
You need to choose tags that look like full-fledged keywords. Let's consider which ones are suitable and which are not
Tags that fit
Also, when there are very few tags, go through them in this format:
capcut pro crack pc / capcut pro crack download for pc / free download capcut pro / download capcut pro crack
Add the words free / download / crack / cracked / for pc / pc crack etc.
at the beginning and at the end. For games, also use the words download / free / cheat(s) / hack(s) / wallhack(s) / aimbot(s) etc.
Also, when you immediately select a tag, immediately check it for a ban using https://github.com/topics/tag.
In the bans and shadows section, I showed what a tag ban looks like.
What to do if your request is unique and there are almost no tags?
Write a request ChatGPT - "Write popular tags on the topic of genshin gayporno crack"
It will give you basic tags, you also check them for a ban and remove garbage tags that are not associated with your topic
Examples of tags that I wrote on popular topics and on NN, which had very few tags
Example
You just need to understand the essence of how to write tags correctly. In an hour, with a trained hand, I was able to make 5-8 packs with tags (1 pack - 20 tags).
When you select tags, be sure to check them on your autoreg, just register it yourself and it doesn't matter whether there is a shadow or not.
Where to publish tags
Publish 1 tag at a time and wait 10-20 seconds - if it kicks you out of your account = tag ban. Don't forget that even if you checked the tag for a ban and it showed you that it is not banned - this does not guarantee that it is not banned, such cases happen very rarely.
My principle for searching and testing tags was as follows:
I search for a tag on the site - I check for a ban (if not banned) - I publish a tag - I search for a new tag at this time, so as not to wait stupidly - I refresh the page and see - banned or not.
You can write your tags in the comments under hide, I can give advice.
Conclusion
Remember that you won't make a mountain of logs right away, you need patience and wait until your topic gets to the top and the logs start pouring in.
If you are very motivated in this, then create more topics and upload them. When you have 300-500 repositories and 10-20-30 of which are repositories in the top - you can easily bring 50-100+ logs every day. Check all your topics 5-7 days after uploading, if the repository is banned - check all the tags - change the banned ones and re-upload.
I can only wish you good luck!
I leave you a link to the project in figma. Where I looked for different icons from programs and games. Figma is very convenient and simple in this regard, you can figure it out even without any skills.
Bonus
https://www.figma.com/design/3nhjN1o7fut8XSzL6qOJxx/Untitled?node-id=0-1&t=yGejQbvKDWTgsXaZ-1
