Fakturownia - 600,000 Businesses, 38 Hours Inside, and the Invoices Built for Payment Fraud
25 minAudio
Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Fakturownia, a Warsaw-based cloud invoicing and accounting platform used by more than 600,000 businesses, has confirmed that an attacker exploited a flaw in its PDF-from-template generation, obtained server access, and over about 38 hours of access copied a large part of its production database. The company says every account is affected. France's VosFactures, which runs on the same platform, has confirmed indirect impact. Timeline (Polish local time, per the company). Sunday 27 September, ~03:20 - unauthorised access begins. Monday 28 September, 13:35 - attacker's IP blocked (detection); ~17:45 - access ends; 18:01 - vulnerability fixed; evening - keys and passwords rotated, traffic moved to rebuilt servers, old servers shut down; 23:10 - customer panel locked; overnight - all customer API tokens replaced. Tuesday 29 September - reported to Poland's data protection authority (UODO), CERT Polska and cybercrime police; public statement 16:15. Thursday 1 October - individual notifications begin; update confirms the incident "concerns every account". What was taken. In full: company and user details (names, tax numbers, emails, phones), bank account numbers including IBAN/SWIFT, salted password hashes, API tokens and integration keys, session IDs, and bank balances where the bank connection was active. By date cut-off (oldest-first download, interrupted; the company says cut-offs may vary by a dozen or so days): full invoices before 22 March 2021, invoice line items before 6 June 2019, counterparties added before 16 October 2024, warehouse documents before 14 July 2023, most export/import files generated up to 6 March 2026, and invoice amounts and descriptive fields across the whole period. About 2,250 accounts lost everything from 2022-2026. Not taken: KSeF e-invoicing certificates, bank logins and card data (not stored), and invoice contents from 22 March 2021 onward other than amounts, descriptive fields and additional-party data. Poland's national e-invoicing system was not breached (Ministry of Finance). No CVE. An actor calling itself "Fingerprint" claimed the attack and 6 TB of invoices; both are unverified claims. No ransom demand. Lessons. Stolen invoices are the raw material for invoice-redirection fraud: use call-back verification for every bank-detail change and dual approval for new payees. Inventory and be ready to rotate every API key connected to your accounting platform. Apply retention limits (APP 11.2). Under the Notifiable Data Breaches scheme, a supplier breach can still be your obligation to assess. Write prompt, full breach notification into supplier contracts. MFA, unique passwords, and sign out all sessions after a provider breach. Visit www.kinsoft.com.au to talk through your security and IT needs. Sources: The Record; Fakturownia incident page (fakturownia.pl/incydent); Niebezpiecznik; Sekurak; Zaufana Trzecia Strona; CyberDefence24; cyberscope.pl; PIT.pl (Ministry of Finance statement); Cyberattaque.org (VosFactures).
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Transcript
From the show. Tap a time to play from there.
I want you to try a little thought experiment with me to kick things off. Okay. I'm game. So imagine for a second that someone out there gets their hands on a copy of every single invoice your business has ever sent. Oh boy. Every single one. Every single one. But, and this is the kicker, they don't have your login passwords. They don't have your corporate credit card details. Right. Just the paperwork. Just the paperwork. Exactly. Just the invoices. this massive digital stack
of paperwork. But I want you to think about what's actually on those pages. Well, it's a lot of data when you really look at it. It is. It's who you bill, exactly how much you bill them, the cadence of those payments, which ones are still unpaid, and crucially, the bank account number sitting right there at the bottom of the page. Yeah, people forget about that part. So take a second to really sit with that. If you're running a business, what could a bad actor actually
do with that specific pile of paper? It's funny because it sounds almost benign at first glance, you know? Right, because it's not a password. Exactly. We are so conditioned to guard our logins, our biometric data, all our direct financial credentials, that we just completely overlook operational data. We just think of it as like administrative exhaust. Yeah, admin exhaust. Perfect way to put it. But in the wrong hands. That mundane paperwork is highly weaponized intelligence.
And that is the exact reality we are looking at today. We're pulling from a really, I mean, eye -opening report from Tech Talks with Kinsoft. This is dated October 9, 2026. It's a fantastic report. It really is. Really detailed. So our mission for this deep dive is to understand a massive, unprecedented cyber breach at this... somewhat obscure Polish invoicing platform. Obscure to us, maybe, but huge over there. Exactly. And more importantly, we're going to look at why this specific breach serves as a glaring wake -up call for, well, literally any business worldwide
that uses cloud accounting software. Which is pretty much everyone at this point. Right. Whether your business runs on Xero, NYOB, QuickBooks, whatever it is. Okay, let's unpack this. So the platform at the center of this event is called Factoronia. And while you might have never heard of it, it is an absolute giant in its region. Yeah, a massive footprint. Right. It's a Warsaw -based software -as -a -service product, and it handles invoicing, accounting, inventory for sole traders and small businesses. We're talking about more than 600 ,000 businesses relying on
this single platform. That's a huge target. And if you add to that its French counterpart, Volfacteur, which hosts over half a million users of its own. I mean, the sheer scale of centralized data here is staggering. It really sets the stage. We are looking at the exact anatomy of modern financial cybercrime here. We really are. Because Factorina has, you know, hundreds of thousands of businesses, all this incredibly sensitive financial data. Yet the way the attackers got into the system is almost embarrassingly mundane. It usually is. The Hollywood image of a hacker
furiously typing green code to smash through a firewall, that is rarely the reality. Right. There's no progress bar saying, hacking the mainframe. Exactly. Modern breaches usually exploit something completely boring that everyone just takes for granted. And the company actually provided a very transparent timeline of the attack, which is wild to read through. It's so detailed. It's great for us, but yeah, pretty scary for them. So it starts on a Sunday. September 27th at 3 .20 a .m. local time. The attacker breached the
system through a flaw in a library used to generate PDF invoices. Just a PDF generator. Literally the tool that takes a blank template and turns it into a PDF so you can, you know, email it to a client. Something every single platform has. Exactly. And through that tiny, innocuous feature, they managed to steal the session signing keys. And with those keys, they just walked straight into the production database. Right through the front door? Well, the side door, really. To me, this is like breaking into a high -security bank
vault by crawling through the pneumatic tube at the drive -thru window. That is a great analogy. I mean, every single invoicing software on Earth has a generate PDF button. How does that become the back door to the entire kingdom? Let's break down why that pneumatic tube reaches all the way into the vault, because it's important. Yeah, please. Think about what a PDF generator actually has to do to render an invoice. It doesn't just take a picture of your screen. Right. It's not a screenshot. No. It needs to assemble a highly complex document from dozens of different data points. It needs your company name, your client's
address, the individual line items, the pricing structure, tax codes, and your bank details. It's pulling from everywhere. Exactly. To get all that, the PDF engine needs high -level read access across multiple disparate relational tables deep inside the core database. It's constantly querying the deepest parts of the system to build that one document. Ah, I see. So it's deeply connected by necessity. Right. So if an attacker figures out how to manipulate that specific query process, say by injecting malicious commands
into the invoice template itself, they suddenly have a straw. drinking directly from the bottom of the database. That is terrifying. Just sipping all the data right out. What's fascinating here is Factorio Nova's response time and the level of transparency they offered after the fact. Yeah. The speed of it all is intense. So they get in early Sunday morning. By Monday at 1 .35 p .m., the platform detects the anomaly and actively blocks the attacker's IP address. Which is a good first step. But the attacker just pivots.
And they maintain access until 5 .45 p .m. that evening. So you have a 38 -hour window where the vault door is just wide open. I mean, 38 hours is a blink of an eye in cybersecurity. Really? Yep. It sounds like a long time to have a burglar in your house. It does. But the dwell time, which is the amount of time an attacker is inside a system before being detected, that's usually measured in months. Oh, wow. Months. Yeah. Discovering an intruder and booting them out in 38 hours is actually an incredibly aggressive response. Well, they didn't stop there. By 6
.01 p .m. on Monday, which is just 16 minutes after the access finally ends, the vulnerability is patched. That's fast. They rotate all the keys and passwords. They literally migrated all of their live traffic over to newly built servers. Wow. Yeah. And by 11 .10 p .m., they've locked down the customer panels and they replaced all the API tokens overnight. That is a monumental engineering effort. They effectively rebuilt the ship while it was taking on water, you know? While under fire, basically. Navigating a live threat environment without totally destroying
the service for their 600 ,000 users. Publishing this to -the -minute timeline, I mean, it really should be the gold standard for incident response. Yeah, it's so rare to see this level of detail. Factoria laid out their exact failure and their exact remediation steps for the world to see. instead of just hiding behind a vague PR statement about a, quote, sophisticated cyber event. Which we see all the time. But even though the speed is impressive, 38 hours is still a long time for someone to be drinking from that database straw, as you said. Right. A lot of data can
flow through that straw. So what did they manage to carry out the door before the platform finally cut them off? Well, the Kinsoft report breaks the stolen data into two distinct categories, and the difference between them is actually critical to understand. Okay, let's look at the first category then. The platform data. So this is the operational data Factoronia holds about its customers, the businesses themselves. Right. The account holders. And this entire category was taken in full. We are talking about company details, tax identification numbers, email addresses,
phone numbers. They got international bank account numbers like IBAN and SWIFT codes. Everything you need to identify a business. Yeah. And they got API tokens, salted password hashes. And for customers who linked their actual banking feeds to the software, they got the live bank balances. Which is highly sensitive. I need to pause here, though, because the report dropped some heavy jargon. Salted password hashes. That sounds like a breakfast order at a diner. I know, it really does. What does that actually mean for the security
of my login? It is one of those terms cybersecurity professionals just throw around, but it's vital to understand. So a responsible software company never saves your actual password in plain text. Right. They don't just have a spreadsheet with password 123 written on it. Exactly. If your password is password 123, they run it through a mathematical blender called a hash function, which turns it into a long scrambled string of random characters. Okay. I'm with you. And you can't unblend it to get the original password back. But if a hacker knows you use password
123, they can run it through the same blender themselves, see if the scrambled strings match, and log in. Oh, because the blender always spits out the exact same scramble for the same word. You got it. To stop that, systems add salt. They throw a random string of extra characters into your password right before blending it. So even if two users have the exact same terrible password, the scrambled result looks completely different in the database because of that random salt? You've got it perfectly. Because Factoronia hashed
and salted the passwords, the attackers can't just log into people's accounts tomorrow. They have the scrambled math, not the keys themselves. Okay, that makes sense. That's a relief at least. But you also mentioned API tokens, and I see that term constantly in these reports. Yeah, that one's a big deal. Think of an API token as a machine -to -machine skeleton key. Skeleton key, okay. You don't want to type your password every single time your accounting software needs to pull a transaction from your bank or push data to your CRM. That would be incredibly annoying.
Right, so you generate an API token. It's basically a digital hall pass that lets two software programs talk to each other securely in the background. The attackers stole those hall passes. Oh, wow. So they could just impersonate the software. Exactly. So Factoridia had to invalidate every single one of them overnight, meaning thousands of businesses woke up to find their software integrations completely broken. Just totally disconnected. Okay, well, that covers the platform data. The second category of stolen information
is the customer's business data. Right, the actual commerce side. The actual invoices, the line items, the client lists. And because the attacker was cut off at that 38 -hour mark, this data pool was bounded by date. They didn't get everything. Right, they ran out of time. But they downloaded the oldest records first. And I really struggled with this part of the source material. Why download the oldest data first? It does seem counterintuitive. Right. If I am a criminal looking to scam a business, wouldn't I want the active unpaid bills from
yesterday? Why am I stealing invoice line items from June 2019? It comes down to the mechanics of database architecture. When an attacker breaches a system and wants to exfiltrate massive amounts of data, they don't sit there clicking download newest on a nice user interface. They're not just using the app like a normal person. Exactly. They write an automated script to scrape the raw database tables. And databases typically assign sequential identification numbers to records, the absolute moment they're created. Okay, so
record number one is the oldest? Record number one is the oldest. Record number 10 million is the newest. A scraping script usually starts at index zero and sequentially vacuums its way up. Ah, so they are just vacuuming the data from the bottom of the barrel up to the top. Exactly the visual. The legacy data is exposed first because it sits at the bottom of the numerical pile. That makes total sense now. Look at what they acquired before Factoronia severed the connection. They pulled full invoice contents from before March 2021, invoice line items from before June
2019, customer and supplier records added before October 2024. It's all historical. Yeah. And most concerning, export and import files up to March 2026, which can contain absolutely massive dumps of historical data. And for about... 2 ,250 incredibly unlucky accounts. The attacker managed to pull absolutely everything from 2022 to 2026. A total compromise. Just devastating for those specific businesses. Absolutely. I
should note the report specifically lists what was not taken. So Polish e -invoicing certificates and bank logins or credit card details simply because the company never stored them in the first place. Which is a good practice. But the scale of what was taken is heavy. An entity going by the name Fingerprint claims to be holding six terabytes of these invoices. Six terabytes. I mean, six terabytes of pure text and PDF data is an almost unfathomable volume of documents. We're talking millions upon millions of pages
of global commerce. It's staggering. And the Polish government is actively involved now, right? The source quotes the deputy prime minister and digital affairs minister Krzysztof Gawowski. Yes, he weighed in pretty heavily. He stated that those responsible are being pursued and will face serious consequences. But he made a pointed remark that the private sector desperately needs to increase its cybersecurity investments. He is highlighting a terrifying structural reality there. The critical infrastructure of global commerce isn't hosted by governments anymore. It is hosted by private software vendors. Right.
It's out of their hands. When an obscure PDF library fails, the wider economy takes the hit. Which brings us to the real danger here. Having gigabytes of old invoices from 2019 sounds incredibly boring to a layperson. I mean, who really cares about a receipt for office supplies from five years ago? It sounds totally useless. Right. But why is this specific pile of paper so uniquely dangerous? An invoicing platform is the ultimate map of your cash flow network. It doesn't just
show how much money you make. What else does it show? It shows exactly who trusts you, how much they trust you with, and the exact communication channels you use to exchange funds. It is the absolute crown jewel for a very specific type of fraud. Here's where it gets really interesting. Because the Kinsoft report connects this directly to business email compromise, or BEC. The scourge of the corporate world. Right. The traditional scam model involves blasting out millions of poorly spelled phishing emails about a frozen
PayPal account, just hoping a fraction of a percent of people click a bad link. The shotgun approach. Yeah, but with this Factoronia data, the attackers don't need to guess. They know your entire business history. Let's walk through how this actually plays out in a corporate office because it's chilling. Imagine an accounts payable clerk sitting at their desk on a Tuesday morning. Okay, setting the scene. They receive an email from a vendor they have paid every month for the last four years. The email contains an invoice. Looks totally normal. Exactly. The invoice number is sequentially
correct. The visual branding is flawless. The amount requested perfectly matches the historical pricing structure. Wow. The language in the email just says, hi, we are currently updating our banking facilities. Please update our routing details in your system before remitting payment for this month. So the clerk looks at it. Everything lines up perfectly with their internal records. So they just update the routing number and hit send. Yep. They've just wired $50 ,000 straight to a criminal. And that historical accuracy is
exactly what bypasses the human firewall. You can spend millions of dollars on the best enterprise -grade antivirus, network monitoring, email filtering. It doesn't matter. Because it's not a virus. Exactly. The firewall lets the email through because it doesn't contain a malicious payload. It is a perfect plain text email that simply contains a lie. It's weaponized context. The attacker leverages the mundane history of your own business to build unshakable trust with your client. They literally use the reality of your past to steal your future revenue. It's incredibly
effective. So knowing the devastating potential of business email compromise, how do you actually survive an event like this? Well, you certainly can't just throw your hands up and say it's out of your control. The Kinsoft report details a very specific survival playbook. Oh, good. We need a playbook. It hinges on the reality that when your software vendor fails, the defensive burden shifts entirely under your shoulders. So if I'm a small business owner listening to this and I wake up to an email from my vendor saying their database has been breached, what is my immediate move? How do I stop my clients
from sending my money to a scammer? Your first move is to implement mandatory callback verification for your own team and demand your clients do the same. Callback verification. What does that look like? This means any time a vendor emails you asking to change their bank details, you pick up the phone and call them to confirm it. Just a phone call. Crucially, you call the number you already have on file in your internal database, never the phone number listed in the email requesting the change. Right, because the email number goes to the scammer. It sounds so incredibly basic,
almost analog, just pick up the phone, but people hate doing it. They really do. They feel awkward calling a vendor to say, hey, did you actually change banks or are you being hacked? It just feels confrontational. Human nature gets in the way of security every time. We have to completely normalize that verification process. Make it an immovable policy requiring dual approval for new payees in your accounting software. No exceptions. The report explicitly says if you only take away one lesson, make it callback verification. It is the only foolproof defense against the contextually
perfect phishing email. The report also brings up auditing your connected apps, which goes back to those skeleton keys. Yes, the API tokens. Factoronia had to scramble to invalidate every single API token to stop the bleeding. If a listener's accounting software got hit tomorrow, they need to know what those skeleton keys are connected to. Right. You can't just guess. You need to open your Xero or your MYOB settings today, look at the connected third -party apps, and figure out who still has access. If there's an integration for a shipping tool you stopped using three years
ago, that API token is just sitting there as a vulnerability. You cannot secure a building if you don't know how many master keys are floating around in the pockets of former contractors. You need to know exactly how fast you can hit the revoke button on those integrations if one of them is compromised. The third major takeaway focuses on data retention, and this ties directly back to the attackers scraping the database from the bottom up. Oh, yes. The legacy data problem. We all treat cloud storage like an infinite digital attic. The Kinsoft report references Australian
Privacy Principle 11 .2, which dictates that entities must take reasonable steps to destroy or de -identify personal information they no longer need. Which nobody does. Right. Keeping tax records for seven years makes sense. But keeping granular invoice line items from a decade ago is just stockpiling ammunition for an attacker. Data is a toxic asset. We have developed a culture of digital hoarding because server space is so cheap. Out of sight, out of mind. Exactly. But if you don't actively need that historical data
to run your business today, you have a security imperative to delete it. As we saw with the 2019 invoices, the legacy data you forgot you even had is exactly what the attackers will walk away with first. Which naturally leads into the notification question. And this brings up some pretty intense legal nuances. It gets complicated here. Yeah. Under European law and under frameworks like the Australian Notifiable Data Breaches Scheme, there is a strict difference between a data processor and a data controller. Factoronia is just the
processor. The business, you, the listener, are the controller. This is where the panic truly sets in for small business owners. Many assume that if their software company gets hacked, the vendor's legal team will handle the fallout. That'd be nice. The law disagrees. You are the entity that collected that personal financial information from your clients. You made the executive choice to store it on Factoronia or Xero or QuickBooks. It's on you. Legally, the duty to assess the risk of serious harm and notify your clients
falls squarely on you. You cannot outsource your legal and ethical liability to your software provider. That is a terrifying realization. Your clients aren't going to be mad at the software company they've never heard of. They are going to be furious with you. Absolutely. Which makes vendor communication absolutely critical. The fifth point. Factorina's very first email to their customers only mentioned that API keys were being rotated for security reasons. It entirely omitted the fact that a massive data exfiltration had just occurred. And that's a huge problem.
Now, Factorina's subsequent emails over the next few days were highly detailed and honest, which actually earned them praise from security commentators. But that first one. But that initial evasive email proves a vital point about enterprise software contracts. You need contractual clauses that demand prompt and full notification in the event of a breach. Not just we're rotating keys. Right. A generic pre -sale security questionnaire won't protect you. You need contractual leverage forcing the vendor to tell you the unfiltered truth the
absolute moment they discover an intrusion. If we connect this to the bigger picture. If we connect this to the bigger picture. The hardest pill to swallow is that there was absolutely no software update, no firewall configuration, and no password manager the end user could have utilized to prevent this breach. Nothing you could do on your end. Nothing. The vulnerability was buried deep inside the vendor's proprietary code. The only actual defense a business has is what the report terms a two -hour plan. A two -hour plan? What does that actually look
like in practice? When that inevitable email arrives notifying you that your vendor has been compromised, you need a predetermined checklist for the next 120 minutes. You rotate your own keys. You proactively warn your customers not to accept any sudden changes to your bank details. You freeze your internal payee modifications. And you trigger your legal notification assessment. You just execute the plan. Exactly. In the middle of a cyber crisis, you will not have the mental bandwidth to figure this out on the fly. So what does this all mean? We've traced the journey
from a tiny, almost invisible flaw in a PDF generation tool to a staggering 38 -hour heist to the exposure of the ultimate toolkit for business email compromise. It's quite a journey. It serves as a stark reminder that our digital supply chains are profoundly fragile. And the mundane paperwork sitting in your accounting software is basically a goldmine waiting to be weaponized against you and your clients. It really requires a fundamental shift in how we view administrative records. Paperwork. is intelligence. Guard it accordingly. I want
to leave you with one final, deeply provocative thought to mull over, and it goes back to the attacker, the entity calling themselves fingerprint. Ah, yes. The plot thickens. They recently gave an unverified interview claiming they didn't execute this breach for a financial gain. They claim they already knew about the PDF vulnerability, reported it to Facturo as a bug, and were completely ignored. Which is a bold claim. Very bold. Their stated motive is that they only stole six terabytes of sensitive financial data to force the vendor to take their bug report seriously. My company
hasn't verified this claim, and frankly, it sounds highly self -serving for a hacker holding six terabytes of stolen data. Yeah, I did it for your own good as a tough sell. Right. But consider the broader implications if they are telling the truth. If we are entering an era where frustrated so -called gray hat hackers. Feel compelled to execute massive economy -rattling cyber heists simply to force tech platforms to patch dangerous vulnerabilities. That's a scary thought. How fundamentally broken is the communication pipeline between independent security researchers and
the corporate giants holding our data? If the tech -savvy community feels they have to burn the village down just to prove to the mayor that the buildings are flammable, we are facing a systemic crisis that no firewall can fix. That leaves you wondering who is actually guarding the vault. and whether they are even listening to the people trying to help them reinforce the door. Thank you for joining us on this deep dive. Keep your curiosity sharp, trust your gut, and pick up the phone when you get an invoice with new bank details. And please, keep your API tokens
Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Japanese home goods company Iris Ohyama (online store operator Iris Plaza) found a suspicious file in an external...
Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Australian online retailer Who Gives A Crap told customers on 7 November 2026 that their information was accessed...
Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Last week in tech, 7 to 14 November 2026. Microsoft's November Patch Tuesday (10 November) fixes well over a...
Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Chainalysis disclosed on 30 October 2026 that an external actor using "offensive agentic techniques" accessed...
Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! NSW Health reported unauthorised access to its Oral Health Fee For Service Scheme website on 29 October 2026;...