惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

小众软件
小众软件
量子位
博客园 - 叶小钗
Apple Machine Learning Research
Apple Machine Learning Research
U
Unit 42
IT之家
IT之家
F
Fortinet All Blogs
GbyAI
GbyAI
MongoDB | Blog
MongoDB | Blog
H
Hackread – Cybersecurity News, Data Breaches, AI and More
大猫的无限游戏
大猫的无限游戏
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
The Register - Security
The Register - Security
NISL@THU
NISL@THU
Webroot Blog
Webroot Blog
A
Arctic Wolf
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
V
Visual Studio Blog
Recent Announcements
Recent Announcements
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
Blog — PlanetScale
Blog — PlanetScale
L
LangChain Blog
P
Palo Alto Networks Blog
Y
Y Combinator Blog
WordPress大学
WordPress大学
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
AWS News Blog
AWS News Blog
有赞技术团队
有赞技术团队
Engineering at Meta
Engineering at Meta
C
Cybersecurity and Infrastructure Security Agency CISA
aimingoo的专栏
aimingoo的专栏
Know Your Adversary
Know Your Adversary
Cyberwarzone
Cyberwarzone
Martin Fowler
Martin Fowler
The Hacker News
The Hacker News
P
Privacy International News Feed
T
Threat Research - Cisco Blogs
G
GRAHAM CLULEY
宝玉的分享
宝玉的分享
博客园 - 聂微东
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
The GitHub Blog
The GitHub Blog
S
Securelist
T
The Exploit Database - CXSecurity.com
T
Threatpost
Microsoft Azure Blog
Microsoft Azure Blog
The Cloudflare Blog
F
Full Disclosure

Wiz Blog | RSS feed

Meet Wiz for M365: Bringing SaaS into the Security Graph How to Harden GitHub Actions: An Updated Guide Bringing Security Visibility to Vercel with Wiz Axios NPM Distribution Compromised in Supply Chain Attack Tracking TeamPCP: Investigating Post-Compromise Attacks Seen in the Wild The Wiz Blue Agent, now Generally Available Beyond the Badge: What Achieving Microsoft’s Certified Software Designation Means for Your Cloud Security Introducing the Green Agent: AI-Powered Remediation for the Cloud Three’s a Crowd: TeamPCP trojanizes LiteLLM in Continuation of Campaign KICS GitHub Action Compromised: TeamPCP Strikes Again in Supply Chain Attack Introducing the Wiz Red Agent- AI-Powered Attacker Introducing Wiz AI Application Protection Platform (AI-APP) Introducing Wiz Agents & Workflows: Security at the Speed of AI AI Runtime Threat Detection: From Input to Real-World Impact Trivy Compromised: Everything You Need to Know about the Latest Supply Chain Attack It’s Official: Wiz Joins Google Understanding and Reducing AI Risk in Modern Applications Introducing Wiz Tenant Manager: Multi-Tenant Management for Federated Organizations The Agile FedRAMP Playbook, Part 4: Reactive Risk Management through Enriched Incident Response Wiz Achieves CPSTIC Certification in Spain Seeing AI Clearly: Building Visibility Across Modern AI Applications The Agile FedRAMP Playbook, Part 3: Preventative Risk Management by building Secure by Design Wiz Leads the 2026 Latio Application Security Report with awards in 4 categories Building an Agentic Cloud Security Ecosystem: A Reference Architecture with Wiz MCP and Infosys Cyber Next The Agile FedRAMP Playbook, Part 2: Proactive Risk Management with Continuous Monitoring Cloud-native Security for your Windows environment: Announcing the Wiz Runtime Sensor for Windows Would You Click ‘Accept’? Automatically detecting malicious Azure OAuth applications using LLMs Wiz Named a Leader in The Forrester Wave™: Cloud Native Application Protection Solutions, Q1 2026 From Detection to Remediation: It’s Time to Rethink AppSec Around Exploitability and Root Cause Fixes The Agile FedRAMP Playbook, Part 1: Why Risk is Your Best Starting Point Introducing AI Cyber Model Arena: A Real-World Benchmark for AI Agents in Cybersecurity Wiz + Spotify Backstage: Security at the Developer’s Desk Building AI Security Together: New Ways to Partner with Wiz for AI Security in 2026 Hacking Moltbook: The AI Social Network Any Human Can Control The Year in Wiz Research: 2025 Most Read Blogs WizExtend is Here: AI and Cloud Security Insights in Your Daily Workflow From Detection to Remediation: Wiz in Your JetBrains IDE Agentic Browser Security: 2025 Year-End Review CodeBreach: Infiltrating the AWS Console Supply Chain and Hijacking AWS GitHub Repositories via CodeBuild A 90-Day Action Plan to Turn Resolutions into Results with Wiz Introducing the Wiz Partner Alliance: A New Chapter for Partner Success Preparing for Post-Quantum Cryptography Wiz Recognized as a 2025 Customers’ Choice in the Gartner® Peer Insights™ Voice of the Customer for CNAPP Expanding the Zero Critical Club to set a new standard for AppSec and SecOps teams Snipping the Long Tail of Shai-Hulud 2.0 Protecting Against Zero-Day Vulnerabilities with SOC-Level ASM Alert MongoBleed (CVE-2025-14847) exploited in the wild: everything you need to know The Kenna Transition: Your Strategic Shift to Exposure Management From MCP to Vibe Coding: Full Endpoint Visibility in Wiz AI Security Bringing Oracle Cloud Identity to Wiz Zero‑Days in the Age of AI: Behind the Scenes of ZeroDay.cloud 2025, with a Record High of CVEs in Critical Cloud Infra Gogs 0-Day Exploited in the Wild Code to Cloud Attacks: From Github PAT to Cloud Control Plane Top AWS re:Invent Announcements for Security Teams in 2025 React2Shell: Technical Deep-Dive & In-the-Wild Exploitation of CVE-2025-55182 React2Shell (CVE-2025-55182): Everything You Need to Know About the Critical React Vulnerability Wiz Product Announcements at re:Invent 2025: Expanding Visibility from Code to Cloud Introducing Wiz SAST: Where Code Risk Meets Cloud Context Wiz Becomes Fastest Security ISV to Reach $1 Billion in AWS Marketplace Lifetime Sales It's Here! Wiz Exposure Management is Now GA Shai-Hulud 2.0 Aftermath: Trends, Victimology and Impact Service Catalog is Here: Expand Risk Visibility for Your Service and Its Dependencies, Simplify Issue Ownership WizOS: Powering Secured Image Adoption with AI 3 OAuth TTPs Seen This Month — and How to Detect Them with Entra ID Logs Mastering Software Governance with Hosted Technologies Inventory Shai-Hulud 2.0 Supply Chain Attack: 25K+ Repos Exposing Secrets Get Certified on Wiz Defend for Threat Detection and Response Blueprint for Security: A Guide to Code, Governance, and Response Frameworks Google Unified Security Recommended Program Names Wiz Among First 3 Strategic Partners Introducing Posture Issues: Transform Security Findings into Actionable Outcomes Empower and Accelerate Your SOC with the Blue Agent Exposure Report: 65% of Leading AI Companies Found with Verified Secret Leaks Wizdom 2025 Product Announcements: Extending the Cloud Operating Model When AI Becomes the Heart of Security: Powering a Future You Can Trust AI-Powered Wiz: From Agents to Everyday Intelligence Defend Agentless Workload Detection: Bringing Visibility to Blind Spots in Threat Detection Securing AI Agents with Wiz AI-SPM Introducing Wiz ASM: Context-Driven Attack Surface Management Securing Critical Infrastructure in the Cloud Era: A Policy and Technology Blueprint How CISOs Should Plan Security Budgets for 2026 Beyond the Checkbox: How Wiz Transforms SOC 2 into a Security Powerhouse Bringing Visibility to Kubernetes: Unified Inventory and Network Insight The Foundation Modern AppSec Is Still Missing: Code to Cloud, Rebuilt the Right Way Dismantling a Critical Supply Chain Risk in VSCode Extension Marketplaces Introducing HoneyBee: How We Automate Honeypot Deployment for Threat Research RediShell: Critical Remote Code Execution Vulnerability (CVE-2025-49844) in Redis, 10 CVSS score Defending against database ransomware attacks AI Security 101: Mapping the AI Attack Surface Introducing zeroday.cloud: First-of-its-kind cloud and AI hacking competition Unifying Cloud Risk and Network Defense: Wiz and Check Point The emerging use of malware invoking AI Wiz achieves FedRAMP High authorization Wiz + HCP Terraform: Close the IaC-to-Cloud Infrastructure Security Gap IMDS Abused: Hunting Rare Behaviors to Uncover Exploits Beyond CVEs: The Exploitation of Everyday Misconfigurations Wiz Research Discovers One in Five Organizations Exposed to Systemic Risks in Vibe-Coded Applications - Here's How to Secure Them Introducing Wiz Incident Response: Your Expert Partner for Cloud Security Incidents Shai-Hulud: Ongoing Package Supply Chain Worm Delivering Data-Stealing Malware DORA Compliance in the Cloud Era: Insights from Deloitte and Wiz How Wiz Customers like Brex and FICO See AI Changing Security
Proof of storage crypto miners
Scott Piper · 2024-02-22 · via Wiz Blog | RSS feed

A 2021 report from Google’s Cybersecurity Action Team mentioned that in 50 compromised Google Cloud instances they had investigated, 86% were used for cryptocurrency mining. It mentioned a lesser-known cryptocurrency they had seen, named Chia. The concept of using compromised resources for cryptocurrency mining is referred to as cryptojacking. There are a lot of different cryptocurrencies, such as Bitcoin, Ethereum, and Monero. These use the CPU or GPU of the machines in what is known as “proof-of-work." This post will explore an alternative cryptocurrency group known as “proof-of-storage", which uses large amounts of storage space instead of compute. Chia is one such cryptocurrency, and one that we’ve detected in customer cloud environments. 

What are proof-of-storage cryptocurrencies, and which are likely to be used in cryptojacking? 

Before I begin, I want to warn cryptocurrency enthusiasts that this post is going to grossly oversimplify a lot of things.  It will also use pricing and stats from the time when it was written. 
 
The total global value for all cryptocurrencies of any type is about $2T, with Bitcoin making up nearly half of that. The market cap for all proof-of-storage coins is less than 1% of that, with Filecoin at $3.8B, Chia at $300M, Signum at $3M, and Arweave, Storj, and Siacoin all under $1M. Some of these coins are referred to as “proof-of-space-time," “proof-of-capacity," and other terms, but for our interests, we’ll use “proof-of-storage" as a generic term for coins that make use of large amounts of storage space (ex. hard drive space). 

Bitcoin was the first cryptocurrency and was launched in 2009. The first proof-of-storage coin was Signum (formerly known as burstcoin) in 2014, with Filecoin released that same year. Chia was created in 2021 by the author of the BitTorrent protocol. 

Many of the proof-of-storage coins are used to store actual data for others. These function like a distributed file storage service. One group (the miners) makes their hard drive space available for others to use, who then pay for that service. Filecoin works like this and has 28 EB of storage space available, of which 2 EB are in use. One EB (Exabyte) is one thousand PB (Petabytes) or one million TB (Terabytes).   

In order to ensure data resiliency, the miners must pay an amount upfront as collateral, and then are fined if they don’t respond to data requests in a timely manner. This helps ensure the miners are really storing the data and making it accessible. The minimum amount of storage miners must make available in Filecoin is about 11 TB, which requires a collateral payment of about $500. Enthusiasts for this cryptocurrency are cringing at how much I have glossed over, but the point is that you need to front some money to begin mining, and that there are penalties if you lose data or otherwise are not able to respond in a timely manner to requests. For this reason, I believe Filecoin and similar coins have not been used for cryptojacking. Cryptojackers have less control over the durability of the resources they steal, and so would be more likely to pay the penalties — therefore this seems like it would be less compelling to them. 

Chia differs from many of the proof-of-storage coins in that it does not store useful data, and therefore there is no collateral money paid up front. If a miner loses the data they were expected to have stored, or they do not respond to requests about it in a timely manner, then they will simply lose the chance to make money. This makes Chia more useful for cryptojackers who may lose access to “their” miners at any time as they are discovered and remediated. 

Interest in different cryptocurrencies ebbs and flows with their prices and difficulty of profiting from mining. Chia’s price has reduced dramatically from around $1500 in 2021, down to around $33 today, which has reduced some of the interest in this cryptocurrency. However, it still seems to be the most compelling proof-of-storage coin for cryptojackers due to there not being a need to pay money upfront. 

Chia mining in the cloud 

Cryptocurrency mining of any sort tends to not be cost effective in cloud environments, and cloud providers ban cryptocurrency mining on their platforms. However, cryptojackers don’t worry about cost effectiveness (because they won’t be paying the bill) or terms of service violations.  

Proof-of-work mining can abuse any sort of compute, such as EC2 instances, containers, or Lambda. Similarly, proof-of-storage could abuse any sort of storage. Therefore, someone could use multiple, massive EBS volumes, or they could use S3, along with many of the other storage options. We’ve seen one tutorial (that was removed) that showed how to mount an S3 bucket as a local filesystem on an EC2 instance and perform mining like that.  

Chia generates files that are 108GB in size. Storing that much data in S3 will result in storage charges of $2.48/mo, in addition to access charges. The estimated earnings from that are $0.03/mo, meaning someone would be losing money by doing this. This is a very bad investment when you have to pay for that cloud bill, but cryptojackers are relying on someone else to pay it. This also may not seem like much money, but keep in mind that this can be scaled dramatically. The cryptojacker might make an impressive $27K/mo by using 110 PB, which will result in a cloud bill of $2.5M/mo, or they could scale that up or down even further. At some point, they would likely disrupt the coin's price by becoming the largest miner, but currently this coin uses 33 EB of storage space across all miners. 

Any sort of storage can be used for this, so one shouldn’t simply watch their S3 bill. As an interesting aside, we found some discussion online of people trying to use Filecoin storage to mine Chia as a way of arbitraging one coin against another. This is not cost effective, however. 

The dangers of proof-of-storage cryptojacking 

There has been a lot of attention paid to the threats of abusing compute for cryptocurrency mining, but much less to abusing storage. One online storage company capped the amount of storage that could be used in their “unlimited tier” in 2023 where they specifically mentioned Chia mining as one of the reasons for that change. As unlimited storage plans have been terminated on other platforms, we wonder if Chia mining was also a reason there. 

Proof-of-storage cryptojacking presents some unique concerns: 

  • When cryptojacking is used against compute resources, there are a number of service quotas on AWS that an attacker is likely to bump into that require them to request limit increases. A common service limit people reach is the maximum of 20 EC2s per region before they need to request an increase from AWS. An S3 bucket does not have similar quotas. Although there are limits on the number of buckets someone can create, there are no limits on the amount of data someone can put into a single S3 bucket. On Azure, there is a limit of 250 storage accounts that can be created per subscription per region, with a 5PB limit per storage account. With roughly 60 regions in Azure, this means an account can use 7.5 EB. GCP doesn’t appear to have storage limits. 

  • When AWS EC2 instances or other compute resources are created, there are CloudTrail events which makes proof-of-work cryptojacking easier to identify and remediate. By default, CloudTrail does not record data level events for S3, and some types of data activity do not have any audit logs. The creation of an S3 bucket or other types of data storage resources will create CloudTrail events, but use of an existing resource may not be logged. 

Detection 

Detection can be done in the following ways: 

  • Cloud users should monitor their costs for any unexpected increases.  

  • The binaries used for cryptocurrency mining can be detected via static or runtime detection based on their hashes or content. Chia is an open-source project, and makes the binaries available for download as releases in their Github repo: https://github.com/Chia-Network/chia-blockchain/releases.  There are also related projects: chiapos, madmax, and bladebit. The large 108GB storage files start with the string “Proof of Space Plot“.

  • Port 8447 (TCP) needs to be open on each miner, so identification of that port being accessible may indicate it is being used for Chia mining. 

  • Network lookups to subdomains of chia.net indicate use of this crypto miner. 

  • Any indications of a compromised user or resources should be investigated. 

  • Wiz customers can use our built-in detections for Chia miners, and check for any workload with port 8447 open

Conclusion 

The use of storage space for cryptomining presents some interesting challenges for defenders, but many of the concepts and defenses against proof-of-work cryptomining carry over. Proof-of-storage cryptojacking is not nearly as popular as proof-of-work, but it is something defenders should be aware of.