Day One

• 4 x Bench

• 4 x Incline Bench

• 4 x Cable Flys

• 4 x Tricep Dumbbell kickbacks

• 4 x Dips

• 4 x Skull crushers

Day Two

• 4 x Lat pulldown

• 4 x Rows

• 4 x Deadlifts

• 4 x Hammer curls

• 4 x Incline DB curls

• 4 x DB preacher curls (2 hammer 2 flat)

Day Three

• 4 x Overhead DB Press

• 4 x Front bar rows

• 4 x Lateral Raises

• 4 x Rear Delt Flys

• 10 x Hanging Leg Raises

Day Four

• 4 x Squat

• 4 x Leg press

• 4 x V Squats

• 4 x Glute Raises

• 8 x Calf raises

Day Five

• 4 x BB Curls Superset Cable pull downs

• 4 x DB Concentration Curls superset Dips

• 4 x  BB Hammers Superset Close grip bench

• 10 x Hanging leg raises

Every day we hitting 10 minutes HIIT on the bike, 30sec on 30 off.

Supplements

Carnitine is the ONLY supplement you need my brothers. Don’t fall for the grift.

Brosciense:

Suppversity blog is the ONLY resource you need.

See you on the other side.

Scope

This playbook is specifically designed to address incident response to a compromized frontend.

1. Preparation

• Audit and Review: Regularly audit frontend code and dependencies for vulnerabilities.

• Monitoring Measures: Setup in-house monitoring to help identification of any unusual activities.

• Incident Response Team: Establish an incident response team to engage in a war room scenario.

• Regularly stocktake node packages: Maintain regular audits and stocktake of NPM packages.

• Store MD5 Hashes: Record and store the MD5 hashes of the web body content on each deployment.

• Maintain access list: Maintain and regularly audit a list of who has access to admin panel.

• Regular Backups: Maintain a staging environment and backups for emergency use.

• Pre-written Comms: Engage legal team to draft pre-written comms to use in case of emergency.

• Maintain contact list: Maintain a contact list with service providers and white-hats.

2. Identification

• Identify the incident from monitoring capability:

  • Inhouse monitoring signals.

• Publicly Identified compromise:

  • Members of the public have identified and alerted to the compromise.

  • A public security service has identified the compromise.

• Identify the changes that resulted from the frontend compromise:

  • Check the DNS change logs of the webpage.

  • Have the MD5 hash changed.

  • Filter through unusual frontend interactions.

  • Identify any new contract addresses on the frontend.

3. Response

• Immediate steps following frontend compromise detection:

  • Secure and isolate affected assets and servers.

  • Alert internal security teams and start emergency protocols.

  • Issue organization-wide notifications to cease all frontend-related operations temporarily.

  • Begin checking the software supply chain for any malicious NPM packages.

  • Check access logs for admin panel.

• Liaise with service providers from contact list for:

  • Assistance in tracking and halting malicious activities.

  • Support in recovering compromised assets, if possible.

  • Advice on fortifying security measures post-incident.

  • Report any phishing contract address to chain abuse

  • If webpage is actively visited and user funds drained, report URL to Metamask Phishing detect.

• Begin distributing pre-written communications:

  • Where possible have legal pre-read and authorize distribution.

  • Use social profiles to distribute initial statement.

4. Recovery

• Analyze the incident to determine:

  • The vulnerability that lead to the exploit.

  • The full extent of damages, including asset loss and data compromise (if any).

  • Necessary improvements in security protocols and staff training for prevention.

• Begin backup deployment and returning webpage to normal operation:

  • Only after access audit and package audit.

  • Only after vulnerability identified and mitigated.

  • Reconfigure DNS settings and review.

  • Remove any reports to MM Phshing Detect (if applicable).

  • Store new MD5 hash.

• Develop a recovery strategy encompassing:

  • Steps for safe resumption of all operations.

  • Stocktake of new and old server addresses following incident.

  • Preventative measures against future incidents (bug bounties etc).

  • Communication plans to restore trust with affected parties.

  

Additional Resources

• Curve Finance Frontend Compromize Incident Report

• Velodrome Frontend Compromize Incident Report

• Package Analysis

• DNS Checker

• Hunting Malicious Packages

• Metamask Eth Phishing Detect

Scope

This playbook is specifically designed to address response to a phishing link being clicked and assets subsequently drained.

1. Preparation

• Compile a detailed inventory of

  • all blockchain assets and domains controlled by the organization.

    • Crucial for avoiding errors with internal digital resources.

  • personnel authorized to manage blockchain transactions and smart contracts.

• Formulate communication templates

  • to quickly alert employees of ongoing phishing attacks targeting the company.

  • for collaboration with hosting and blockchain service providers against malicious entities.

  • to inform external stakeholders about potential security threats.

• Create a new hot-wallet

  • write down seed phrase

  • quickly send any remaining funds from compromized wallet/s

2. Identification

• Identify the transaction hash that resulted from the phishing incident:

  • Filter though unusual smart contract interactions.

  • Requests from unknown wallet addresses.

  • Unexpected transaction signing requests.

• Identify the front end and domain that incited the phishing incident:

  • Using recent browser history.

  • Inspect recent emails that may have transported the link.

  • Triage domains though Virus Total and other providers.

3. Response

• Immediate steps upon a phishing attack detection:

  • Secure and isolate affected assets and wallets.

  • Alert internal security teams and start emergency protocols.

  • Issue organization-wide notifications to cease all blockchain-related operations temporarily.

  • Pause any active contracts (if possible).

  • Begin sending any remaining assets to new hot-wallet

• Liaise with blockchain networks or service providers for:

  • Assistance in tracking and halting malicious activities.

  • Support in recovering compromised assets, if possible.

  • Advice on fortifying security measures post-incident.

• Report the phishing link, contract and or wallet address:

  • Upload URL to virus total and other providers.

  • Create a pull request to MM phishing detect and add the URL.

4. Recovery

• Analyze the incident to determine:

  • The point of entry and methods used in the phishing attack.

  • The full extent of damages, including asset loss and data compromise (if any).

  • Necessary improvements in security protocols and staff training for prevention.

• Develop a recovery strategy encompassing:

  • Steps for safe resumption of all operations.

  • Stock-take of new and old wallets following incident.

  • Preventative measures against future incidents.

  • Communication plans to restore trust with affected parties.

Additional Resources

• MetaMask Eth Phishing Detect

• Wallet Guard

• MetaSleuth