Team attribution
Our public company attribution is The Offensive360 Team. Existing articles retain their recorded bylines, including research-team labels. A byline identifies the article’s attribution; it does not establish who discovered a vulnerability or independently reproduced it. Use the company profile for reusable descriptions and official links.
Using product and technical guidance
Use the product pages and a scoped evaluation to confirm supported languages, enabled checks, finding evidence and deployment requirements for your configuration. Educational articles and code examples are starting points: check the relevant framework and version, adapt the guidance to your application, and test the resulting behavior before deployment.
Vulnerability advisory analysis
CVE articles in the vulnerability analysis section are presented as advisory analysis. Consult vendor advisories, CVE records and patch references where supplied to check affected versions and remedies. Original discovery or local reproduction requires explicit credit and supporting details in the individual article; neither should be inferred from the section name or a team byline.
Publication and update dates describe the article. They do not, by themselves, mean every example was executed or every claim was rechecked. Use any article-specific testing notes and limitations to understand what was assessed.
Request a correction
Email [email protected] with the page URL, the statement you believe needs correcting, and a supporting reference or a small, non-sensitive example. Address the request to The Offensive360 Team. Keep credentials, private source code and personal data out of the message.