CyberKareemContact Abdullah
Menu

Professional enquiries, assessments & disclosure

Start with the problem. Keep the first message simple.

For a professional opportunity, security assessment, collaboration, or responsible disclosure, choose the relevant path and share enough context to identify the right next step. Sensitive material can move to an agreed channel after the initial conversation.

Direct business email

Copy the address now, or continue to the optional prepared briefs below.

info@cyberkareem.com

Routed contact workflow · 01

One starting point. Three clear routes.

Choose a route below. The active brief, safety guidance, and prepared message will stay together here. Every route remains readable when browser scripting is unavailable.

Route 01 · Professional

Start a career or professional conversation.

This route is for recruitment, employment, speaking, collaboration, and other professional opportunities. A concise first message is enough to establish context and choose the next step.

Recipient
info@cyberkareem.com
Suggested subject
Professional opportunity enquiry
Next action
Share the opportunity and why it may fit.

Security testing scope, target details, and authorization belong in the assessment route.

Useful first-message context

  • Your name, organization, and role
  • The position, collaboration, or conversation you have in mind
  • The expected responsibilities or professional context
  • Location, remote or on-site expectations, and time zone
  • The expected conversation or decision timeframe
  • A public job description or organization link, when available
Route 02 · Assessment

Tell me what needs to be assessed.

Use this route for an authorized security assessment, scoped review, or consulting enquiry. Share the risk surface, ownership, desired outcome, and timing without including live target details. This first message starts a fit check, not an instant booking.

Recipient
info@cyberkareem.com
Suggested subject
Security assessment enquiry
Next action
Send a structured first message.

Targets, credentials, source code, personal data, and vulnerability evidence should wait for an agreed private channel.

Useful first-message context

  • Your name, organization, and role
  • The assessment track and any relevant platform, cloud provider, chain, or toolchain
  • A high-level asset type and approximate scope
  • Whether the environment is staging or production
  • The desired outcome, timing, and time zone
  • Who owns or can authorize the assets
Assessment tracks available
  • Web Application & API Assessment
  • Mobile Application Security Assessment
  • Network, Identity & Wireless Assessment
  • Application Security Review & Advisory
  • Cloud Security Review & Scoped Assessment
  • Solidity/EVM Smart Contract Security Readiness Review
  1. 01

    Fit check

    Confirm the risk surface, authorization owner, timing, and whether the requested work matches the available assessment track.

  2. 02

    Scope conversation

    Agree targets, access, exclusions, safety boundaries, communication, and the result your team needs.

  3. 03

    Written proposal

    Document the test plan, deliverables, schedule, retest terms, and commercial conditions before work begins.

Route 03 · Disclosure

Request the private channel before sending details.

Ordinary email is not a confidential report intake. Use the initial message to confirm the product, recipient, and a suitable private route. Technical evidence can follow after the channel is agreed.

Recipient
info@cyberkareem.com
Suggested subject
Responsible disclosure channel request
Next action
Initiate disclosure safely.

Do not include exploit code, credentials, personal data, or unpatched technical detail in the initial message.

Disclosure expectations

  • Confirm the affected product or project at a high level
  • Establish the authorization and recipient context
  • Request a private channel before sending technical evidence
  • Share only the minimum evidence needed to establish impact
  • Avoid real-user data, persistence, and service disruption
  • Coordinate publication timing with the responsible maintainer

Public contact & identity · 02

Secondary public channels.

LinkedIn, GitHub, X, and Discord support identity checks, public project context, and community conversation. They are not substitutes for the business-email options on this page.

LinkedIn

Professional identity, career context, and general conversation. Use the prepared email paths above for opportunities or assessment enquiries.

opens in a new tabDiscord community

Community conversation and general questions. The public invite is not a confidential assessment or reporting channel.

opens in a new tabGitHub

Best for open-source project context and maintainer-visible technical discussion that is already safe to make public.

opens in a new tabX

Public updates, research notes, and a secondary way to confirm identity.

opens in a new tab