hashpwn

Terms of Service & Privacy Policy Effective Date: Aug 31, 2025 Welcome to hashpwn.net (“we,” “our,” or “us”). By accessing or using hashpwn.net or any of its subdomains (collectively, the “Services”), you agree to comply with and be bound by these Terms of Service. This includes, but is not limited to, the forum and any Services we may provide under the hashpwn.net domain. If you do not agree, please discontinue use of the Services. 1. Eligibility You must be at least 18 years old to register for or use any hashpwn.net Services. By using our Services, you represent that you meet this requirement. 2. User Conduct When using any hashpwn.net Service, you agree not to: Post, share, or request personally identifiable information (PII). Share, request, or distribute illegally obtained data (e.g., combo lists, stolen data, etc). Engage in hate speech, harassment, or unlawful activities. Attempt to compromise, disrupt, or misuse any Service we provide. Post, share, request, or link to any sexually explicit, pornographic, or sexually suggestive content. Our Services are intended for ethical cybersecurity research, discussion, and learning. Illegal activity is strictly prohibited. 3. User Content You retain ownership of any content you post, upload, or submit to hashpwn.net Services. By submitting content, you grant hashpwn.net a non-exclusive, worldwide license to store, display, and distribute your content as necessary to operate and provide the Services. Requests for deletion of publicly posted content will be honored, except in rare cases where retention is required for legal, security, moderation, or administrative reasons (e.g., evidence of abuse). Account deletion and personal data removal requests will always be honored. 4. Privacy & Data Collection We respect your privacy. We collect basic technical information such as IP address, cookies, browser type, and usage analytics. We use this information only for site functionality, security, and moderation. We may log usage data to maintain service quality. We do not sell, rent, or share your information with third parties for advertising or marketing purposes. Users may request removal of their personal data. 5. Disclaimer of Warranties All Services provided by hashpwn.net are offered “as is” and without warranties of any kind, whether express or implied. We do not guarantee uptime, availability, or error-free operation for any Service. Use of hashpwn.net Services is at your own risk. 6. Limitation of Liability To the fullest extent permitted by law, hashpwn.net, its owners, administrators, moderators, and affiliates are not liable for any damages arising from use of our Services, including but not limited to loss of data, downtime, security issues, or service interruptions. 7. Termination We reserve the right to suspend, restrict, or terminate accounts or access to any hashpwn.net Service at our discretion for violations of these Terms or other reasons deemed necessary to protect the community and infrastructure. 8. Changes to the Terms We may update these Terms at any time. Changes will be posted on this page with a new effective date. Continued use of our Services after updates are posted constitutes acceptance of the revised Terms. 9. Contact For questions, concerns, or requests, please contact: @cyclone (Admin/Owner)

root:$6$NDHTuwWaT/qizX0O$qWlRjrw7f7LLSHt1WX7EPGX4lRanYgNt32dsXaLenRq14d6QkqDdSdJXELLCahCjdkw0T0jFPv/g9/OHfZI1J0

MetaMask Staking Infrastructure Breach Triggers Mass Validator Exits [image: 1790957820799-dcb0ddfa-cc34-466c-8d9d-278a24193145-image.jpeg] MetaMask has disclosed an infrastructure security incident affecting its Ethereum staking operation, prompting the company to begin exiting thousands of validators as a precaution. The incident does not appear to affect normal MetaMask wallets, seed phrases, or customer wallet funds. MetaMask says it has identified no immediate threat to MetaMask wallets. Instead, the compromise involves MetaMask Staking, formerly Consensys Staking, which operates Ethereum validators for clients including Lido. On-chain analysis found that an attacker was able to redirect block rewards from MetaMask-operated validators to an attacker-controlled wallet. Researchers identified 18 diverted payments totaling approximately 0.36 ETH. Although the amount stolen was small, the attacker apparently gained enough access to change validator fee-recipient settings or otherwise cause validators to sign registrations pointing to the attacker. MetaMask responded by exiting affected validators because potentially compromised Ethereum validator signing keys cannot simply be rotated. Independent Bitquery analysis identified approximately 16,965 validators holding 565,056 ETH, worth roughly $1.5 billion at the time, that had exited or entered the exit queue. MetaMask has not officially confirmed those totals. Importantly, the attacker could not simply withdraw the staked ETH because MetaMask does not control its clients' withdrawal keys. No validators were reported as slashed. MetaMask has not yet disclosed how the attacker initially gained access or whether validator signing keys were actually stolen. Sources: MetaMask: User Update - Infrastructure Security Incident https://metamask.io/en-GB/news/user-update Lido: MetaMask Staking Precautionary Out-of-Order Exits https://research.lido.fi/t/security-disclosure-metamask-staking-precautionary-out-of-order-exits/11961 BleepingComputer: MetaMask Discloses Security Incident Affecting Its Infrastructure https://www.bleepingcomputer.com/news/security/metamask-discloses-security-incident-affecting-its-infrastructure/ Bitquery: MetaMask Staking Incident - 17,000 Validators, 0.36 ETH https://bitquery.io/investigations/metamask-staking-incident

CELF + heap: ~4-9 rules/s -> ~50-80 rules/s on RTX 3060 Ti After switching to a lazy heap (instead of a list scanned linearly against fixed upper bounds), average selection speed jumped from 4-9 rules/s to 50-80 rules/s (~6-20x, roughly 10x sustained over a full run at 65 rules/s avg). Reason for the speedup: the old approach had to rescore more and more candidates on GPU each round, because their upper bounds went stale as the active set shrank. The heap always keeps the tightest known bound on top and lets a round end as soon as the popped candidate's exact gain beats the next-best bound — most rounds now finish with 0-1 extra GPU dispatch instead of a full scan over all candidates. Tip: the upper-bound pass (stage 1, where the heap is built) scales with wordlist size, since every candidate is scored against the full resident wordlist. Running stage 1 against a smaller/more targeted wordlist speeds up the heap build and greedy selection noticeably — worth doing if you don't need the full wordlist's coverage resolution for the initial bound estimate. Run stats: (1M candidate rules — top-scored candidates taken from a prior rank run's output, fed into postprocess/CELF; 56.8M-entry cracked universe (hashmob.large.found),for heap build hashmob.mini.found was used, RTX 3060 Ti): Hash table build: 72.5s (vectorized, one-time) Upper-bound pass: 977 batches in 1:55 (8.49 batch/s) Greedy select: 150,000 rules in 38:19 → 65.23 rules/s avg Covered 56,111,301 / 56,857,388 cracked entries (98.7%) with those 150k rules No coverage matrix allocated at any point (RAM or disk) — memory stayed O(n_rules) + O(universe bits) Note: the 1M candidates aren't a random/full rule space — rank already individually scores and ranks rules first (by Combined_Score), and CELF then picks a redundancy-free subset from that pre-filtered top-N pool. So the heap/recompute speedup here is specifically for the second-stage max-coverage selection, on top of whatever rank already narrowed down. See heaped*.rule's in benchmark. heaped_top150000.rule is available here

Escrow ID# 93377 • Algorithm: md5($plaintext.$salt), -m 10 • Total hashes: 23 • Price per hash: $0.9997 • Escrow URL: https://hashes.com/en/escrow/item/?id=93377 • Download hashes: 93377_10.zip

Scheduled Host Maintenance Our host will be performing scheduled maintenance that requires a reboot of the VPS hosting hashpwn. During this maintenance, the forum and related hashpwn services will go offline temporarily. Expected downtime is less than 30 minutes, although we have not been given an exact ETA for when the reboot will occur. This notice is just to give everyone a heads up.