#1 (Пишем свой брутфорс. Руководство для начинающих) - Dec 31, 2023
---
/threads/104897/
Source: user_agent = random.choice(['Mozilla/5.0', 'Chrome/83.0.1'])
PAID
#2 (Детальный разбор xss уязвимостей) - Jan 1, 2024
---
/threads/104943/
Source: stumejournals.com/journals/confsec/2019/4/pdf
mdpi.com/2227-7390/10/20/3787
PAID
#3 (Разбираемся в SQL и CSRF уязвимостях на практике) - Jan 2, 2024
---
/threads/104968/
Source:
PAID
#4 (Path traversal attack) - Jan 5, 2024
---
/threads/105103/
Source: research.cs.wisc.edu/mist/SoftwareSecurityCourse/Chapters/3_3-Directory-Traversal.pdf
PAID
#5 (Хакаем darkboys666 или раскручиваем Local File Inclusion до Remote Code Execution) - Jan 6, 2024
---
/threads/105230/
Source: blog.injectexp.dev/unwind-local-file-inclusion-before-remote-code-execution/02/rce/
PAID
#6 (Пентестим веб сайт на joomla. Детальная статья) - Jan 9, 2024
---
/threads/105379/
Source:
PAID
#7 (вебсайты с помощи sql инъекции. Практическое руководство) - Jan 12, 2024
---
/threads/105666/
Source:
PAID
#8 (Как Используется ChatGPT в кибербезопасности) - Jan 17, 2024
---
/threads/106032/
Source: ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=10198233
PAYMENT REJECTED
#9 (Секреты безопасных веб приложений на JavaScript. Гайд для новичков) - Jan 22, 2024
---
/threads/106419/
Source: PAYMENT REJECTED
#10 (Практика создания веб-сканера уязвимостей на примере сканера из [ // XSSware]) - Mar 24, 2024
---
/threads/111226/
Source:
PAID
#11 (Ресерч на комплексную тему: SECaaS когда безопасность становится умной. Как ИИ защищает данные в облачную эпоху) - Jul 14, 2024
---
/threads/118872/
Source:
PAYMENT REJECTED
#12 (Fileless атаки как смысл жизни: подробный разбор) - Jul 25, 2024
---
/threads/119583/
Source:
PAID
#13 (Кушаем APT на завтрак — раскрываем все аспекты, векторы атак и многое другое) - Jul 27, 2024
---
/threads/119682/
Source: plurilock.com/deep-dive/advanced-persistent-threat-apt/
techtarget.com/searchsecurity/definition/advanced-persistent-threat-APT
PAYMENT REJECTED
#14 (Понедельник — день тяжелый. Разбираем все техники СИ) - Jul 28, 2024
---
/threads/119729/
Source:
PAYMENT REJECTED
#15 (Well, well, well. Обижаем ИИ разными способами) - Aug 9, 2024
---
/threads/120503/
Source:
PAID
#16 (Когда ИИ забывает, кто здесь главный) - Aug 9, 2024
---
/threads/120893/
Source:
PAID
#16 (Как создать идеального советчика по технологиям: Веб-приложение с ИИ, которое не требует кофеина!)
---
/threads/121060/
Source:
PAID
#17 (От новичка до код-гения: Создаём ИИ-ассистента для тренировок и не скучаем)
---
/threads/121163/
Source:
PAID
Good afternoon, I didnot write a detailed judgement on the substance of the articles but purely I allotted myself 2 min for each article with basic plagiarism checkers. most of the article is generic (no useful actual technical details) newspaper style articles copy pasted from news sites, wikipedia, research paper abstracts and first introduction section paragraphs, generated/modified by a neural network, fileless malware written in python, writing a Gemini LLM API wrapper, APT, EDR, XDR, NGAV, horses in a vacuum etc. Of course, no one hates writers who organize, translate, collect, discuss interesting articles from other sources but this is not very good to not cite original authors and even more to ask for a payment from the admin. This doesn't mean the requirement for an article is fuzzing for an unpatched dos use after free in ffmpeg. But there are already lots of other interesting articles/discussions/questions here already.
The author should continue writing, it is great for the writer to study and for the forum, but cite the original authors with links + don't write what is just research paper introduction garbage, horses in a vacuum, don't even write topics on creating flask routes, interaction with llm api. Don't just explain each line of code, each parameter to the function, or even blocks of code, how to parse command line args, or how to convert byte endianness. I suggest the author to study the threads on the forum, read textbooks (not newspaper websites), and ask/answer questions, practice first rather than writing articles. This applies to pure translators as well. Then regarding money, it flies to you slowly, but this will not even be from the articles then)
And this topic brings the discussion of raising the bar for article entries. But that is not the original intention I started this topic with. The is a message in general for the authors) thank you
---
/threads/104897/
Source: user_agent = random.choice(['Mozilla/5.0', 'Chrome/83.0.1'])
PAID
#2 (Детальный разбор xss уязвимостей) - Jan 1, 2024
---
/threads/104943/
Source: stumejournals.com/journals/confsec/2019/4/pdf
mdpi.com/2227-7390/10/20/3787
PAID
#3 (Разбираемся в SQL и CSRF уязвимостях на практике) - Jan 2, 2024
---
/threads/104968/
Source:
PAID
#4 (Path traversal attack) - Jan 5, 2024
---
/threads/105103/
Source: research.cs.wisc.edu/mist/SoftwareSecurityCourse/Chapters/3_3-Directory-Traversal.pdf
PAID
#5 (Хакаем darkboys666 или раскручиваем Local File Inclusion до Remote Code Execution) - Jan 6, 2024
---
/threads/105230/
Source: blog.injectexp.dev/unwind-local-file-inclusion-before-remote-code-execution/02/rce/
PAID
#6 (Пентестим веб сайт на joomla. Детальная статья) - Jan 9, 2024
---
/threads/105379/
Source:
PAID
#7 (вебсайты с помощи sql инъекции. Практическое руководство) - Jan 12, 2024
---
/threads/105666/
Source:
PAID
#8 (Как Используется ChatGPT в кибербезопасности) - Jan 17, 2024
---
/threads/106032/
Source: ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=10198233
PAYMENT REJECTED
#9 (Секреты безопасных веб приложений на JavaScript. Гайд для новичков) - Jan 22, 2024
---
/threads/106419/
Source: PAYMENT REJECTED
#10 (Практика создания веб-сканера уязвимостей на примере сканера из [ // XSSware]) - Mar 24, 2024
---
/threads/111226/
Source:
PAID
#11 (Ресерч на комплексную тему: SECaaS когда безопасность становится умной. Как ИИ защищает данные в облачную эпоху) - Jul 14, 2024
---
/threads/118872/
Source:
PAYMENT REJECTED
#12 (Fileless атаки как смысл жизни: подробный разбор) - Jul 25, 2024
---
/threads/119583/
Source:
PAID
#13 (Кушаем APT на завтрак — раскрываем все аспекты, векторы атак и многое другое) - Jul 27, 2024
---
/threads/119682/
Source: plurilock.com/deep-dive/advanced-persistent-threat-apt/
techtarget.com/searchsecurity/definition/advanced-persistent-threat-APT
PAYMENT REJECTED
#14 (Понедельник — день тяжелый. Разбираем все техники СИ) - Jul 28, 2024
---
/threads/119729/
Source:
PAYMENT REJECTED
#15 (Well, well, well. Обижаем ИИ разными способами) - Aug 9, 2024
---
/threads/120503/
Source:
PAID
#16 (Когда ИИ забывает, кто здесь главный) - Aug 9, 2024
---
/threads/120893/
Source:
PAID
#16 (Как создать идеального советчика по технологиям: Веб-приложение с ИИ, которое не требует кофеина!)
---
/threads/121060/
Source:
PAID
#17 (От новичка до код-гения: Создаём ИИ-ассистента для тренировок и не скучаем)
---
/threads/121163/
Source:
PAID
Good afternoon, I didnot write a detailed judgement on the substance of the articles but purely I allotted myself 2 min for each article with basic plagiarism checkers. most of the article is generic (no useful actual technical details) newspaper style articles copy pasted from news sites, wikipedia, research paper abstracts and first introduction section paragraphs, generated/modified by a neural network, fileless malware written in python, writing a Gemini LLM API wrapper, APT, EDR, XDR, NGAV, horses in a vacuum etc. Of course, no one hates writers who organize, translate, collect, discuss interesting articles from other sources but this is not very good to not cite original authors and even more to ask for a payment from the admin. This doesn't mean the requirement for an article is fuzzing for an unpatched dos use after free in ffmpeg. But there are already lots of other interesting articles/discussions/questions here already.
The author should continue writing, it is great for the writer to study and for the forum, but cite the original authors with links + don't write what is just research paper introduction garbage, horses in a vacuum, don't even write topics on creating flask routes, interaction with llm api. Don't just explain each line of code, each parameter to the function, or even blocks of code, how to parse command line args, or how to convert byte endianness. I suggest the author to study the threads on the forum, read textbooks (not newspaper websites), and ask/answer questions, practice first rather than writing articles. This applies to pure translators as well. Then regarding money, it flies to you slowly, but this will not even be from the articles then)
And this topic brings the discussion of raising the bar for article entries. But that is not the original intention I started this topic with. The is a message in general for the authors) thank you
and even before on that on blogspot, I doubt you even know what that means, its out of your generation, son. I am your daddy. Sit on my lap. "/sbin/init" - Конор Макгрегор youtube.com/watch?v=YezMl2zi5Gs
