Ndm448 EXPOSED: .ndm448 Files, +README-WARNING+.txt, and thomasandersen70@onionmail.org

You open Documents the way you did yesterday. The first photo should still be 1.jpg. The snapshot should still be 2.png. The vacation shot should still be vacation.jpg. The invoice should still be invoice-2026.pdf. Instead every familiar name has a victim ID, an inbox, and a second ending tacked on. 1.jpg is now 1.jpg.[2AF20FA3].[thomasandersen70@onionmail.org].ndm448. 2.png is now 2.png.[2AF20FA3].[thomasandersen70@onionmail.org].ndm448. A small text file named +README-WARNING+.txt is sitting in the same folder, as if it has always belonged there.

That is the trap, not a glitch.

This page is for the hour those names appear. It is not a miracle key. It is a map of the trap, so the note does not become your incident plan.

Overview

Ndm448 ransomware locks the files first. Then it keeps the old name and the old type, and hangs a victim ID, the inbox thomasandersen70@onionmail.org, and .ndm448 on the end. Then it drops +README-WARNING+.txt and talks like a recovery desk. Then it changes the desktop wallpaper so the same squeeze follows you even if you close the folder. The note is a storefront. It opens Dear Management. It says the network is compromised, critical data was leaked, and files are encrypted. It tells you the only move is to write that inbox, or add a qTox ID if mail is silent for 12 hours. It forbids renaming, third-party tools, and a restart. It prints a 4-day leak clock and a 7-day sample clock. It never prints a $ figure. It never prints a wallet. It never prints a Session ID. It never names a leak blog. This page will not invent those missing pieces.

If you are staring at a pile of .ndm448 files and that text note, you are in a ransom incident, not a broken disk and not a Windows pop-up. The folder is the evidence. The note is a checkout. Stay with the folder, not with the script.

The first tell is the rename. In the sample used for this page, 1.jpg becomes 1.jpg.[2AF20FA3].[thomasandersen70@onionmail.org].ndm448. 2.png becomes 2.png.[2AF20FA3].[thomasandersen70@onionmail.org].ndm448. Other files in the same folder follow the same shape: original name, then [ID].[thomasandersen70@onionmail.org].ndm448. You can still read what the file used to be. You cannot open it. Windows may call the type an NDM448 File and offer a useless “choose an app” box. An app cannot talk locked bytes back into a JPEG. There is 0% chance Photos can open 1.jpg.[2AF20FA3].[thomasandersen70@onionmail.org].ndm448 because you picked a viewer.

The second tell is the note. After the files are locked, the malware drops +README-WARNING+.txt into the same folders. README sounds like documentation. WARNING sounds like a safety brief. Put them together and the first English you can still read after the photos break is a sales flyer. The flyer is meant to be opened. It is not meant to be trusted.

The body of that sample is long on purpose. It greets Dear Management. Then three bullets: your network infrastructure has been compromised, critical data was leaked, files are encrypted. Then the pitch: the best and only thing you can do is contact us to settle the matter before any losses occurs. Then Mail : thomasandersen70@onionmail.org. Then a 12-hour silence rule. If you do not receive a response within 12 hours, your letter may not have arrived, and they print an alternative: Chat qtox, a qtox.github.io line, and Our chat ID : 40E320AC41C066E58264ABF8A6B47A93F69DE2BE30FF94AE701EE15ED856FF5BB76A6B2068A4. Then a forbidden list. Then an explanation that talks like a penetration report. Then a to-do list that is just “write us, buy the tool, skip everyone else.” Then two “possible decisions.” Then a 7-day sample threat. Then a responsibility block that threatens keys, sale, disclosure, government mail, competitors, and clients. That is the whole costume.

There is no printed $ ransom. There is no Bitcoin wallet. There is no Session handle. There is no named leak blog. This page will not invent them. A missing $ is not a puzzle you solve by guessing a number. A missing wallet is not a coupon. A missing Session ID is not a riddle. The flyer already named the only doors it wants: that onionmail inbox, and that qTox ID if the inbox stays quiet. Walking through those doors is the product.

Public detections do not agree on the family name, and this page will not pretend they do. Some writeups place Ndm448 with Makop. Antivirus names on the same kind of sample use Phobos labels, including Win32/Filecoder.Phobos.E and Ransom:Win32/Phobos.PB!MTB. Other detections stay generic, such as Win32:Fasec [Trj] and HEUR:Trojan-Ransom.Win32.Generic. Both family words are sitting in public labels. This page reports both. It does not pick one.

That is the whole pitch. A locked folder of .ndm448 names. A +README-WARNING+.txt file that talks like a recovery brief. A wallpaper that repeats the squeeze. An inbox. A qTox ID. A 12-hour mail fuse. A 4-day leak clock. A 7-day sample clock. No $ sticker. No wallet. No Session. No leak blog. There is no public free decryptor known for this strain. There is no reason to mail thomasandersen70@onionmail.org today because a text file told you to.

The .ndm448 name is the first warning

Most lockers pick an extension so you notice the change in seconds. This one uses .ndm448, and it does not stop there. It also stamps a short ID and the contact inbox into the filename, so the listing itself becomes a billboard. You do not have to decode anything. You can still see 1.jpg inside 1.jpg.[2AF20FA3].[thomasandersen70@onionmail.org].ndm448. You can still see 2.png inside 2.png.[2AF20FA3].[thomasandersen70@onionmail.org].ndm448. You can still see the invoice year. The familiar words are still in the folder. The files are not familiar anymore.

Do not treat that readable name as a fix. Do not strip .ndm448 off the end and expect Photos or Excel to open the file. Do not delete the [2AF20FA3] block because it looks like junk. Do not delete [thomasandersen70@onionmail.org] because it looks ugly. Do not run a bulk “extension fixer” you found in an ad. The name is a label. The lock is in the content. Editing the label can make a later trusted tool have a harder time matching the file to what it was. Leave the locked copies as they are until you have a clean machine and a plan that does not start in a criminal inbox.

The extra ending also does advertising. Anyone who sees 1.jpg.[2AF20FA3].[thomasandersen70@onionmail.org].ndm448 next to +README-WARNING+.txt can pretend they already have your case. A later fake helper will quote the extension, the ID, and the inbox back to you as if that were expertise. Those strings are public. They are sitting in the folder. Quoting them proves nothing except that they can read a listing.

+README-WARNING+.txt is a sales floor, not a help file

The ransom note is a plain text file with a name that sounds like documentation and a siren at the same time. +README-WARNING+.txt wants the first click after the panic. Plenty of real software drops a README. Plenty of real alerts use WARNING. This one uses both habits against you. It is meant to be the first English you can still read when the photos will not open.

Double-clicking it opens Notepad. That is why a panicked first click feels like opening the help page. It is not help. It is the demand, written so it looks official enough to follow. The filename is built to look like paperwork. Plus signs. README. WARNING. A .txt ending Windows already trusts. Paperwork is easier to obey than a threat.

Keep the file on disk. Then close it. Do not treat it as a set of steps you should follow. Do not tidy the filename. Do not shorten it to “the readme” when you write the incident down. Copy +README-WARNING+.txt the way you would copy a serial off a stolen laptop. That string is how a responder matches this locker. It is not a coupon you redeem by mailing thomasandersen70@onionmail.org.

Dear Management is a shout, not a briefing

The first line of the sample is not a diagnosis. It is a costume. Dear Management does the same job a fake letterhead does on a scam invoice. It names the reader as a company, even if the machine is a home PC. Then three short bullets name the disaster: compromised, leaked, encrypted. You are supposed to stop thinking and start obeying.

The shout is also a brand. Later search ads will quote Dear Management. Later “helpers” will paste “critical data was leaked” so they sound close to your folder. Anyone can copy a headline. Copying those three bullets does not mean they can reverse .ndm448. It means they read the same note you did, or they read a screenshot of it.

If the shout is sitting in more than one folder, that is normal for this family. Lockers drop the same text in many places so you cannot miss it. Finding five copies is not five incidents. It is one incident with a loud flyer. Keep one clean copy as evidence. You do not need to open every copy. You do not need to compare them in mail to thomasandersen70@onionmail.org.

thomasandersen70@onionmail.org is checkout, not support

The printed contact is thomasandersen70@onionmail.org. Copy that string exactly. Do not “correct” the spelling. Do not swap it for a lookalike that a later email suggests. That inbox is the aisle. A private mailbox puts you in a room they own, on an account they can delete, with a thread they can screenshot and reuse. Email would feel like a ticket. This email is not a ticket. It is how a locked photo becomes a negotiation.

Do not open a fresh mail account because the note said to. Do not send a test file to prove you are a real victim. Do not paste a folder listing into a new message. Do not argue about a $ figure they never printed. Those addresses belong to the people who locked the files. Writing them is the product.

The handle is branding, the same way .ndm448 is branding. Anyone can stand up a lookalike inbox after a wave of locked folders. Writing the first message does not start a warranty. It starts a conversation you cannot enforce. The 12-hour line is how they make that first message feel late before you have even pressed Send.

The qTox ID is a second door, not a rescue

If the inbox stays quiet for 12 hours, the note does not tell you to wait. It tells you to add a chat. Chat qtox. A qtox.github.io line. Then Our chat ID : 40E320AC41C066E58264ABF8A6B47A93F69DE2BE30FF94AE701EE15ED856FF5BB76A6B2068A4. Copy that ID exactly. Do not shorten it. Do not swap an O for a 0. Do not invent a Session handle because a later helper says “Tox is down, use Session.” The published sample has no Session ID. This page will not invent one.

qTox is still a room they own. Adding that ID is still contact. It is the backup checkout. A long hex string looks technical. Technical looks like support. It is still the people who locked 1.jpg.[2AF20FA3].[thomasandersen70@onionmail.org].ndm448. Do not install a chat client because a ransom note printed a download line. Do not paste that ID into a client “just to see if it is online.” Seeing a green dot is not a decryptor.

Keep the ID as evidence. Treat it the same way you treat the inbox: an identifier for a report, not a door you walk through at midnight. A stranger who later sends a different Tox ID, a Telegram handle, or a Session string is rewriting the flyer so they can stand in the aisle.

12 hours is a fuse, not a courtesy

The note says if you do not receive a response within 12 hours, your letter may not have arrived. That sentence does two jobs. It makes waiting feel like a mistake you already made. It also pushes you into the second channel they already prepared. Twelve hours is not a service-level agreement. It is a fuse glued to a second door.

Do not start a kitchen-timer because a text file said 12 hours. Do not send a second mail, then a Tox add, then a third mail, because the clock made you feel ignored. Silence from a criminal inbox is not a delivery error. It is one possible outcome of writing people who do not owe you a reply. The CISA StopRansomware Guide is blunt about this kind of squeeze. Paying does not ensure the files come back, does not ensure the systems are clean, and does not ensure anyone on the other side keeps a promise. A 12-hour “try again” is not a vendor. It is the checkout, staged in two rooms.

THE FOLLOWING IS STRICTLY FORBIDDEN is a scare list

The note prints a forbidden list in capital letters. 1.1 EDITING FILES ON HDD. Renaming, copying, or moving any files could DAMAGE the cipher and decryption will be impossible. 1.2 USING THIRD-PARTY SOFTWARE. Trying to recover with any software can also break the cipher. 1.3 SHUTDOWN OR RESTART THE PC. Boot and recovery errors can also damage the cipher. Sorry about that, but doing so is entirely at your own risk.

Read the tone, not the costume. “Sorry about that” is not kindness. It is how a locker tries to freeze you in the chair. A person who is afraid to restart is a person who keeps reading the flyer. A person who is afraid to copy a file is a person who will not make a clean evidence copy later on a machine that is not theirs. The scare is the point.

Leaving the locked names alone is still good advice, for a different reason than they want. Renaming is not a repair. Miracle decryptors from ads are often a second scam. Calling that out does not mean you should obey the rest of the flyer. It does not mean you should skip an official report. It does not mean you should skip counsel. The people who locked the files do not get a vote on who you tell, and they do not get a vote on whether the machine can be powered down for a real response.

The leak claim is a second squeeze

The note does not stop at locked photos. It adds a leak. It says they already downloaded a huge amount of critical data and analyzed it. Now its fate is up to you: deleted, sold, or shared with the media. It lists the kinds of files they “usually steal”: databases, legal documents, personal information, audit reports, audit SQL, financial documents, work files, corporate correspondence, any backups, confidential documents. That list is a menu of fears. It is not a completed theft report.

Treat the leak line as attacker copy, not as a finished publication. Naming “the media” does not prove a reporter is waiting. Naming “supervisory organizations” does not prove a regulator has a package. It also does not prove they have nothing. It is a missing proof dressed as a deadline. This page will not invent a leak blog to finish that sentence. The published note does not name one.

The to-do list piles on. Contact us as soon as possible. Contact us only in our live chat, otherwise you can run into scammers. Purchase our decryption tool. There is no other way. Avoid third-party negotiators and recovery groups, because they can become the source of leaks. That last line is how they try to cut you off from anyone who is not them. It is still a text file in Documents. It is still sitting next to 1.jpg.[2AF20FA3].[thomasandersen70@onionmail.org].ndm448.

4 days and 7 days are printed clocks

Under NOT MAKING THE DEAL, the note prints a 4-day clock. After 4 days starting tomorrow, your leaked data will be Disclosed or sold. They will also send the data to all interested supervisory organizations and the media. The decryption key will be deleted permanently. Losses can be measured based on your annual budget. That last line is a $ hint without a $ number. It wants you to invent the bill yourself.

Then section 4 prints a second clock. All leaked Data samples will be Disclosed in 7 Days if you remain silent. Your decryption keys will be permanently destroyed at the moment the leaked Data is Disclosed. Two clocks. Two threats. Zero proof. Zero $ sticker. Do not start a personal countdown because a forum post said “they only wait two days.” The published flyer already printed 4 days and 7 days. Leave the rest uninvented.

Do not try to beat those clocks by sending a first message “just to stop the leak.” That first message is the product. It tells them a victim is live. It tells them a victim reads English. It tells them a victim is afraid of the media line. You can still tell the people whose files lived on the machine. You can still tell counsel. You can still tell an official desk. The people who locked the files do not get a seat in that call.

No printed $ price is not kindness

The note never prints a $ ransom. It never prints a bitcoin total. It never prints a wallet. It tells you to write, then “purchase our decryption tool,” then figure the rest out in a negotiation they own. That missing number is not mercy. It lets whoever answers set a price after they see who you are. A family photo folder and a contractor laptop can get two different asks. Inventing a $ amount here would only help the costume.

Do not convert a made-up $ figure in your head. Do not let a later “helper” invent one and call it the original Ndm448 price. The published flyer left the amount off. A blank price plus a 4-day leak plus a 7-day sample threat is how they make you feel late before you have even spoken. You do not owe that feeling a payment. There is 0% chance a $ you guessed from “annual budget” is a real invoice.

Makop on the writeup, Phobos on the scanner

Family names are where this strain gets messy, and the mess is worth keeping. Some public writeups call Ndm448 a Makop variant. Antivirus detections on matching samples use Phobos names, including ESET’s Win32/Filecoder.Phobos.E and Microsoft’s Ransom:Win32/Phobos.PB!MTB. Avast has used Win32:Fasec [Trj]. Kaspersky has used HEUR:Trojan-Ransom.Win32.Generic. Those labels can all be true as labels. They are not a reason to pick a fan team.

Do not rewrite your incident report to match the family you like better. Do not search only “Makop decryptor” and ignore Phobos pages, or the other way around. Do not let a broker say “this is definitely Phobos, we have the Phobos key” because a scanner printed that word. Do not let a second broker say “this is Makop, ignore Phobos” because a blog printed that word. The evidence on disk is still the same: names ending in .ndm448, the [ID].[thomasandersen70@onionmail.org].ndm448 pattern, and +README-WARNING+.txt. This page reports both family words. It does not pick one.

The wallpaper is the same flyer on the glass

Ndm448 also changes the desktop wallpaper. That wallpaper is not a second incident. It is the same squeeze painted on the desktop so you cannot look away. It is meant to make closing Explorer feel useless. It is meant to make +README-WARNING+.txt feel like the only remaining document on the machine. Photograph the wallpaper from a phone if you can do it without mailing that inbox. Then leave it. You do not need to argue with a background image. The evidence is still the .ndm448 names and the note.

Notice what this page will not do. It will not invent wallpaper text that was not copied here. Changing the picture back does not unlock vacation.jpg.[2AF20FA3].[thomasandersen70@onionmail.org].ndm448. It only removes one piece of evidence if you do it before you photograph the screen. Take the photo first. Then leave the glass alone until you have a clean machine and a real plan.

How The Attack Works

The shop is simple once you stop reading it as a rescue. Lock the files. Brand the names with a victim ID, thomasandersen70@onionmail.org, and .ndm448. Drop +README-WARNING+.txt. Paint the wallpaper. Greet Management. Claim a leak. Point recovery at that inbox. Print a 12-hour fuse and a qTox ID as the backup door. Forbid renaming, miracle tools, and a restart. Print a 4-day leak and a 7-day sample clock. Leave the $ blank. Leave the wallet blank. Leave Session blank. Leave the leak blog unnamed. Then wait for someone else to sell a family name.

1. The lock keeps the old name so you recognize the loss

Ndm448 encrypts the files it wants as leverage, then appends a tagged ending. That is why 1.jpg is still readable as 1.jpg.[2AF20FA3].[thomasandersen70@onionmail.org].ndm448, and why 2.png is still readable as 2.png.[2AF20FA3].[thomasandersen70@onionmail.org].ndm448. The operators want you to inventory the damage in seconds. They want you to see the photo, the snapshot, the vacation shot, and the invoice in one glance. A coded filename can confuse you. A readable filename makes you feel the theft. Stamping the inbox into the name makes the checkout feel already attached to every file.

If only one folder looks wrong, do not assume the rest of the disk is safe. Ransomware walks trees. It hits Documents, Desktop, Pictures, Downloads, and any drive letter it can reach, including a USB stick you forgot was plugged in. Do not plug in a copy “just to check.” Checking is how the extra copy gets the same .ndm448 ending.

Double-clicking a renamed file does not bring the photo back. The thumbnail may already look broken. Excel may ask for a workbook that is still sitting in the same folder, only the bytes inside are no longer a workbook. That broken open is the first proof. The second proof is the extra ending. Together they are enough. You do not need to mail thomasandersen70@onionmail.org to confirm what you are looking at.

2. +README-WARNING+.txt takes the first click

Once the names are branded, the malware needs a voice. Other families cover the glass and stop there. This one drops a text file with plus signs in the name so it sorts near the top. +README-WARNING+.txt feels like the machine itself left you a note. It feels like a help file you must finish before you can do anything else. That is how a locked photo folder starts to feel like a checkout.

The note is also a hiding trick. While you are reading it, you are not calmly sorting 1.jpg.[2AF20FA3].[thomasandersen70@onionmail.org].ndm448 next to 2.png.[2AF20FA3].[thomasandersen70@onionmail.org].ndm448. You are not photographing Explorer. You are not calling someone who can help. The demand is in Notepad. The evidence is in the listing. Read the note as a sales flyer. Then close it. Keep the file. The files next to it still matter more than the shout.

Notice what the note does not give you. It does not give you a company, a refund policy, or a way to prove the other side will ever send a key. It does not give you a $ price. It does not give you a test decrypt. It does not give you a wallet. It does not give you a Session ID. It gives you a tone that says this is already decided. That tone is the product.

3. Dear Management turns a break-in into a meeting

The greeting is a costume. Dear Management. Compromised. Leaked. Encrypted. The best and only thing you can do is contact us. That paragraph is meant to make a home PC feel like a board incident, and a small office feel like a finished case file. You are supposed to feel that the only adult move left is to write.

The explanation block keeps the costume going. The security of your IT perimeter has been compromised, it says, and it is not perfect at all. We encrypted your workstations and servers to make the fact of the intrusion visible. We spent a lot of time researching the most important directories. That is sales copy wearing a consultant jacket. It is not a lab report. It is not a reason to skip copies that were never mounted. It is not a reason to skip a trusted decryptor project later if one appears.

4. thomasandersen70@onionmail.org is the door they want you to walk through

The recovery step in the sample is mail. Mail : thomasandersen70@onionmail.org. That is the whole first door. It looks like support because support uses email. Criminal shops use email too, because a thread is where a missing $ figure becomes a negotiation and a locked photo becomes a sample they asked you to attach.

Do not write that inbox. Do not create a throwaway account “just to see.” Do not send a screenshot of Explorer to prove the lock. They already chose the extension. They already chose the note filename. They already stamped the inbox into 1.jpg.[2AF20FA3].[thomasandersen70@onionmail.org].ndm448. A photo of +README-WARNING+.txt sitting next to that name does not make you a verified customer. It makes you a person still following the flyer.

If someone later says they will “talk to Ndm448 for you” through that same address, that is a broker pitch. Brokers need you in the same funnel. You do not owe them a seat. Report the incident through official desks. Let counsel decide if contact is ever required for a specific legal reason. That decision is not yours to make from the Documents folder at midnight.

5. The qTox ID is the backup door

The second door is chat. The note prints a qTox page line and this exact ID: 40E320AC41C066E58264ABF8A6B47A93F69DE2BE30FF94AE701EE15ED856FF5BB76A6B2068A4. That string is not a password that unlocks .ndm448. It is a handle. Adding it is still contact. Installing the client is still following the flyer.

Do not add that qTox ID. Do not hunt a “closer” Tox ID because a later message says this one is stale. Do not jump to Session, Telegram, or a random onion because someone claims the original chat is down. The published sample has one inbox and one qTox ID. It has no Session. This page will not invent a third channel. Keep the printed ID for the incident record. Leave the client uninstalled.

6. 12 hours, 4 days, and 7 days keep you from thinking

The clocks are stacked. Twelve hours to treat silence as a mail failure. Four days starting tomorrow before leaked data is disclosed or sold. Seven days before samples are disclosed and keys are destroyed. Each number closes a door. The 12-hour line closes “maybe I should wait overnight.” The 4-day line closes “maybe I should call counsel first.” The 7-day line closes “maybe I should report this.” You are supposed to feel that every honest step is already too slow.

Do not add extra clocks the note never printed. Do not send a small file because a later message offered a test decrypt the original note never printed. Do not “test” a smaller $ amount to see if they answer. A test payment is still a payment. It still tells them this victim pays. The published flyer never printed a first price. Double of a blank number is still a blank number.

7. The forbidden list keeps you still

The forbidden list is meant to freeze the room. Do not rename. Do not copy. Do not move. Do not use third-party software. Do not shut down. Do not restart. Sorry about that. That last apology is theater. A locker that needs you panicked also needs you seated, reading, and ready to write.

You can still refuse the shop without bulk-renaming the pile. Leave 1.jpg.[2AF20FA3].[thomasandersen70@onionmail.org].ndm448 named as it is. Leave +README-WARNING+.txt where it is. Leaving names alone is not the same as obeying a criminal checklist. It is how you keep the evidence readable. Powering down for a real response is still a decision for you, counsel, or an incident lead. The flyer does not get that vote.

8. WIN-WIN DEAL is checkout copy

The note offers two “possible decisions.” Not making the deal: disclosure, sale, media, keys gone, losses measured against your annual budget. Making the win-win deal: the only working decryption tool, a how-to-use manual, guarantees of deletion with a log, secrecy, removal of traces, and a security report on how to fix your breaches. That is a storefront. It is not a contract. A “log provided” from the people who locked the files is not an audit.

The responsibility block is the same product in a louder voice. Breaking critical points of this offer will cause deletion of keys, immediate sale or complete disclosure, and notification of government supervision agencies, your competitors, and clients. That paragraph is meant to make an official report feel dangerous. It is still a paragraph. It is not a court date. It is not a confirmed publication. It is not a reason to mail thomasandersen70@onionmail.org.

9. Family labels will be sold back to you

After a ransomware incident, search results fill up with pages that say Makop, pages that say Phobos, and pages that say both. Some of that disagreement is ordinary detection noise. Some of it is a sales hook. A shop that needs you to pick a family can then sell the matching “key.” This strain gives them two words to work with. Do not help them.

Report what is on the disk. Names like 1.jpg.[2AF20FA3].[thomasandersen70@onionmail.org].ndm448. Note filename +README-WARNING+.txt. Inbox thomasandersen70@onionmail.org. qTox ID 40E320AC41C066E58264ABF8A6B47A93F69DE2BE30FF94AE701EE15ED856FF5BB76A6B2068A4. Then, separately, report that writeups have used Makop and that scanners have used Phobos. Keep both. If a later helper says you must pick one before they can help, they are selling a label, not a decryptor.

10. Third parties will sell an Ndm448 conversation

Search ads will fill up with companies that say they can decrypt Ndm448 or “all .ndm448 files.” Some of those shops are ordinary overpriced consultants. Plenty are a second scam. They will quote +README-WARNING+.txt so they sound close to the case. They will mention Dear Management. They will mention the 12-hour rule. They will mention the 4-day leak. They will mention Makop. They will mention Phobos. They will mention thomasandersen70@onionmail.org as if they already called the original crew. They will ask for a sample file, a remote-access session, or a deposit.

A demo that “unlocks one file” is not proof they can unlock the vacation photo. Anyone can open one junk file they control. Anyone can send you a wallet string that makes an exchange window appear. An exchange window is not Photos opening vacation.jpg again. If a later message skips the original inbox and asks for coin over ordinary mail, that is still the same market, or a copycat standing in the same doorway. Do not answer. Do not help them set a wallet the public copy left off on purpose. Do not help them invent a Session ID the public copy never printed.

A real public decryptor, when one exists, shows up on an official project page that already existed before your incident. It does not need a $ send. It does not need that inbox. It does not need that qTox ID. If the pitch is “we can decrypt, pay us first,” you are still in the market the ransomware created. There is no public free decryptor known for this strain. Until a trusted project publishes one, treat any site that says “we already have the Ndm448 key” as a second sales pitch.

11. Payment and mailing that inbox close nothing

Paying a stranger for a private key is not a guarantee. The people who send the note can take the money and disappear. They can send a string that only makes a decryptor show an error. They can come back later and lock the same machine again. A mail thread makes that outcome easier, not harder. You cannot leave a review on a criminal inbox. You cannot leave a review on a qTox ID.

Mailing thomasandersen70@onionmail.org is the free version of the same dead end. Adding 40E320AC41C066E58264ABF8A6B47A93F69DE2BE30FF94AE701EE15ED856FF5BB76A6B2068A4 is the same dead end in a different app. There is no public free decryptor known for this strain. Starting a thread does not rebuild a JPEG. It only keeps you in their story while the rest of the disk still needs a real plan.

If this is a company machine, tell counsel and your incident lead. If this is a home PC, tell the people whose files lived on it. Change passwords from a clean device. Watch bank and email alerts. Opening that inbox again is not useful work. Adding that qTox is not useful work. It is the checkout, even when the flyer never printed a $ figure and never printed a wallet.

What To Do If Your Files End in .ndm448

Do not pay. Do not email thomasandersen70@onionmail.org. Do not add that qTox ID. Do not invent a wallet, a Session ID, a leak blog, or a $ figure to finish +README-WARNING+.txt. Do not send a test file. Do not send proof of payment. If you already sent a message before you found this page, stop there. Do not pay a deposit to “hold the original deal” for anyone who quotes the note.

• STEP 1: Use Rkill to terminate suspicious programs.
• STEP 2: Use Malwarebytes to remove for Ransomware and Unwanted Programs
• STEP 3: Use HitmanPro to remove Trojans and other Malware
• STEP 4: Use AdwCleaner to remove Malicious Browser Extensions and Adware
• STEP 5: Perform a final check with ESET Online Scanner
• STEP 6: Restore the files encrypted by ransomware

STEP 1: Use Rkill to terminate suspicious programs.

In this first step, we will download and run Rkill to terminate suspicious programs that may be running on your computer.

RKill is a program that was developed at BleepingComputer.com that attempts to terminate known malware processes so that your normal security software can then run and clean your computer of infections. When RKill runs it will kill malware processes and then removes incorrect executable associations and fixes policies that stop us from using certain tools.

1. Download Rkill.

   You can download RKill to your computer from the below link. When at the download page, click on the Download Now button labeled iExplore.exe. We are downloading a renamed version of Rkill (iExplore.exe) because some malware will not allow processes to run unless they have a certain filename.

   

   RKILL DOWNLOAD LINK
   (The above link will open a new page from where you can download Rkill)

2. Run RKill.

   After downloading, double-click the iExplore.exe icon to kill malicious processes. In most cases, downloaded files are saved to the Downloads folder.
   The program may take some time to search for and end various malware programs.

   

   When it is finished, the black window will close automatically and a log file will open. Do not restart your computer. Proceed to the next step in this guide.

STEP 2: Use Malwarebytes to remove Ransomware and Unwanted Programs

In this second step, we will install Malwarebytes to scan and remove any infections, adware, or potentially unwanted programs that may be present on your computer.

Malwarebytes is one of the most popular and trusted anti-malware tools for Windows — and it’s completely free for removing infections. It catches threats that many antivirus programs miss, including adware, browser hijackers, and trojans. Follow the steps below to scan and clean your PC in just a few minutes.

1. Download Malwarebytes

   Click the button below to download the latest version of Malwarebytes for Windows from the official source. The free version is all you need — it will scan your computer and remove adware, browser hijackers, and other malicious software at no cost.

   

   DOWNLOAD MALWAREBYTES FOR WINDOWS (FREE)
   
   (The link opens in a new page where your download will start)

2. Install Malwarebytes

   When the download finishes, open your Downloads folder and double-click the MBSetup file. If Windows shows a User Account Control pop-up, click “Yes” to allow the installation.

   

3. Follow the On-Screen Prompts to Install Malwarebytes

   The setup wizard will walk you through a few quick screens:

   • Choose where you’re installing the program — “Personal Computer” or “Work Computer” — then click Next.

     

   • Malwarebytes will now install on your device. This usually takes under a minute.

     

   • When installation is complete, the “Welcome to Malwarebytes” screen will open automatically.

     

   • On the final screen, click Open Malwarebytes to launch the program.

     

4. Enable “Scan for Rootkits”

   Before scanning, turn on rootkit detection so Malwarebytes can find even the most hidden threats. Click the Settings gear icon on the left side of the screen.

   

   In the settings menu, find “Scan for rootkits” and click the toggle so it turns blue.

   

   Done? Click “Dashboard” in the left pane to return to the main screen.

5. Start the Scan

   Click the blue Scan button. Malwarebytes will automatically update its virus database and start checking your computer for malware.

   

6. Wait for the Scan to Finish

   The scan checks your entire system for browser hijackers and other malicious programs, so it can take several minutes. Feel free to do something else — just check back occasionally to see the progress.

   

7. Quarantine the Detected Threats

   When the scan is done, you’ll see a list of everything Malwarebytes found — malware, adware, and potentially unwanted programs. Click the “Quarantine” button to remove all of them at once.

   

   Malwarebytes will now remove the malicious files and registry entries and move them safely into quarantine.

   

8. Restart Your Computer

   Some threats can only be fully removed after a reboot. If Malwarebytes asks you to restart, click Yes. Once you’re logged back in, your PC is clean and you can continue with the next steps in this guide.

   

STEP 3: Use HitmanPro to remove Rootkits and other Malware

In this third step, while the computer is in normal back, we will download and run a scan with HitmanPro to remove Trojans, rootkits, and other malicious programs.

HitmanPro is a second-opinion scanner — it’s designed to catch what your main antivirus might have missed. Instead of relying on a single detection engine, it checks the behavior of files in the locations where malware usually hides. Anything suspicious gets sent to the cloud, where it’s analyzed by two of the best antivirus engines available: Bitdefender and Kaspersky.

Good news: scanning is completely free, with no limits. You only need a license when it’s time to remove what was found — and even then, you can activate a free one-time 30-day trial to clean your PC at no cost. (A full license is $24.95 per year for 1 PC.)

1. Download HitmanPro

   Click the button below to download HitmanPro. Remember — the scan is free, so you have nothing to lose by checking your PC.

   DOWNLOAD HITMANPRO (FREE SCAN)
   (The link opens in a new page where your download will start)

2. Install HitmanPro

   When the download finishes, open your Downloads folder and double-click the file: “hitmanpro.exe” on 32-bit Windows, or “hitmanpro_x64.exe” on 64-bit Windows.

   

   If a User Account Control pop-up asks whether HitmanPro can make changes to your device, click “Yes” to continue.

   

3. Follow the On-Screen Prompts

   On the HitmanPro start screen, click “Next” to begin the system scan. No lengthy setup required — it goes straight to work.

   

   

4. Wait for the Scan to Finish

   HitmanPro will now check your computer for malicious programs. This usually takes just a few minutes thanks to its cloud-based scanning.
   

5. Review the Results and Click “Next”

   When the scan is done, HitmanPro will show you everything it found. Click “Next” to remove the detected threats.

   

6. Click “Activate Free License”

   To remove the malicious files, click the “Activate free license” button. This starts your free 30-day trial — no payment details needed — and unlocks the full cleanup.
   

   When the removal is complete, HitmanPro will show a summary of everything it cleaned. Click Next, then click Reboot if prompted. If there’s no reboot prompt, just click Close — your PC is clean.

STEP 4: Use AdwCleaner to remove Malicious Browser Extensions and Adware

In this next step, we will use AdwCleaner to remove malicious browser policies and unwanted browser extensions from your computer.

AdwCleaner is a free on-demand scanner that specializes in adware, browser hijackers, and unwanted toolbars — the exact threats that mainstream antivirus programs often miss. It also includes tools that repair the damage malware leaves behind, like hijacked browser settings and malicious policies. It’s a quick scan that’s well worth running.

1. Download AdwCleaner

   Click the button below to download AdwCleaner — it’s free, portable, and requires no installation.

   

   DOWNLOAD ADWCLEANER (FREE)
   (The link opens in a new page where your download will start)

2. Run AdwCleaner

   Open your Downloads folder and double-click the file named “adwcleaner_x.x.x.exe“. There’s no installation — the program starts right away.
   

   If Windows asks whether you want to allow AdwCleaner to run, click “Yes“. When the license agreement appears, click I agree to continue.

   

3. Enable “Reset Chrome policies”

   This setting removes malicious browser policies — a trick malware uses to lock your browser settings so you can’t change them back. Click “Settings” on the left side of the window, then turn on “Reset Chrome policies“.

   

4. Start the Scan

   Click “Dashboard” on the left side of the window, then click the “Scan” button.

   

5. Wait for the Scan to Finish

   AdwCleaner will now check your computer for adware and other malware. This usually takes only a few minutes — it’s one of the fastest scanners around.

   

6. Quarantine the Detected Threats

   When the scan finishes, AdwCleaner will list everything it found. Click the “Quarantine” button to remove all the malicious items at once.

   

7. Click “Continue” to Finish the Cleanup

   Save any open work first — AdwCleaner needs to close your open programs before it can clean. When you’re ready, click the “Continue” button.
   

   AdwCleaner will now delete all detected malware from your computer. If it asks you to restart your PC, allow it — your computer will be clean when you log back in.

STEP 5: Perform a final check with ESET Online Scanner

This final step involves installing and running a scan with ESET Online Scanner to check for any additional malicious programs that may be installed on the computer..

ESET Online Scanner is a free second-opinion scanner that performs a deep, full-system check for viruses, trojans, rootkits, and other malware. We use it as the final step because it’s thorough — if anything slipped past the previous scans, ESET will find it. A clean result here means your computer is malware-free.

1. Download ESET Online Scanner

   Click the button below to download ESET Online Scanner.

   

   DOWNLOAD ESET ONLINE SCANNER (FREE)
   (The link opens in a new page where your download will start)

2. Run the Installer

   When the download finishes, open your Downloads folder and double-click “esetonlinescanner.exe“.
   

3. Install ESET Online Scanner

   On the start screen, select your language from the drop-down menu and click Get started.

   

   On the Terms of use screen, click Accept.
   

   Choose your preferences for the Customer Experience Improvement Program and the Detection feedback system (either choice is fine), then click Continue.
   

4. Start a Full Scan

   Click Full Scan — this checks your entire computer, not just the common hiding spots.

   

   Select Enable for Detection of Potentially Unwanted Applications — this lets ESET catch adware and bundled junk programs, not just viruses. Then click Start scan.

   

5. Wait for the Scan to Finish

   ESET will now check every file on your computer. Because it’s a full scan, this can take a while — often an hour or more, depending on how much data you have. Leave it running in the background and check on it from time to time.

   

6. Review the Results

   When the scan completes, the Found and resolved detections screen appears. Any threats found were automatically cleaned and quarantined — there’s nothing extra you need to do. Click View detailed results if you want to see exactly what was removed.
   

   If ESET found nothing — congratulations, your computer has passed the final check and is malware-free.

STEP 6: Restore the files encrypted by ransomware

Unfortunately, in most cases, it’s not possible to recover the files encrypted by this ransomware virus because the private key which is needed to unlock the encrypted files is only available through the attackers. However, below we’ve listed three options you can use to try and recover your files.

Option 1: Search a decryption tool for this ransomware

The cybersecurity community is constantly working to create ransomware decryption tools, so you can try to search these sites for updates:

• https://id-ransomware.malwarehunterteam.com/
• https://decrypter.emsisoft.com/
• https://noransom.kaspersky.com/
• https://www.avast.com/ransomware-decryption-tools

Option 2: Use EaseUS Data Recovery Wizard Free to recover the encrypted files

EaseUS Data Recovery Wizard Free can restore files and repair corrupted files with simple clicks. Its powerful scanning algorithms can identify and retrieve huge file type library, including all of the popular video files, audio files, photos, and document formats.
While the free version only allows you to recover 2 GB of data, this can be helpful to see if the recovery is possible and restore back the most important files from your computer.

1. Download EaseUS Data Recovery Wizard Free.

   You can download EaseUS Data Recovery Wizard Free by clicking the link below.

   

   EASEUS DATA RECOVERY WIZARD FREE DOWNLOAD LINK
   (The above link will open a new page from where you can download EaseUS Data Recovery Wizard)

2. Double-click on the EaseUS Data Recovery Wizard Free setup file.

   When EaseUS Data Recovery Wizard Free has finished downloading, double-click on the setup file to install EaseUS Data Recovery Wizard on your computer. In most cases, downloaded files are saved to the Downloads folder.

   

   You may be presented with a User Account Control pop-up asking if you want to allow EaseUS to make changes to your device. If this happens, you should click “Yes” to continue with the EaseUS Data Recovery Wizard Free installation.

3. Follow the on-screen prompts to install EaseUS Data Recovery Wizard.

   When the EaseUS Data Recovery Wizard installation begins, click on the “Install Now” as seen in the image below.
   

   When your EaseUS Data Recovery Wizard installation completes, click the “Start Now” button to start the program.
   

4. Select a location to start recovering the encrypted files.

   Choose the drive or folder where you are the encrypted files that you want to recover and click “Scan“.
   

5. Wait for the EaseUS Data Recovery Wizard scan to complete.

   EaseUS Data Recovery Wizard will now scan your computer files that can be restored. This process can take a few minutes, so we suggest you do something else and periodically check on the status of the scan to see when it is finished.
   

6. Find the files you want to recover.

   When the EaseUS Data Recovery Wizard scan is finished scanning it will show a screen that displays the files that can be recovered. This tool can recover a lot of data, use the “Filter” button to quickly filter specific file types and find the files that you want to recover.
   

   Click the “Preview” button or double-click on a file for a full preview.
   

7. Select your files and click “Recover”.

   Finally, select the the files you want to recover and click “Recover“.
   
   Choose a safe location to save all the files.
   
   The free version only allow you to recover 2 GB of data, however, this will allow you to recover the most important files and see if EaseUS Data Recovery Wizard can correctly recover them.
   

Option 3: Try to restore your files with ShadowExplorer

This ransomware will attempt to delete all shadow copies when you first start any executable on your computer after becoming infected. Thankfully, the infection is not always able to remove the shadow copies, so you should continue to try restoring your files using this method.

1. Download ShadowExplorer.

   You can download ShadowExplorer from the below link.

   SHADOW EXPLORER DOWNLOAD LINK
   (This link will open a new web page from where you can download “ShadowExplorer”)

2. Install ShadowExplorer.

   Double-click on the ShadowExplorer-x.x-setup file to start the installation process, then follow the on-screen promts to install this program.
   

3. Select snapshot date.

   Open ShadowExplorer and then from the top bar select the drive where the files that you want to save are located, then select from the snapshot available one previous to this infection.

   

4. Export the files that you want to recover.

   Once you have found a copy of the original file or folder, right-click on it and the select “Export”. A window will prompt you where you want to save the file or folder.
   

Keep every .ndm448 name exactly as it is. Keep at least one locked sample, including a documented name such as 1.jpg.[2AF20FA3].[thomasandersen70@onionmail.org].ndm448 or 2.png.[2AF20FA3].[thomasandersen70@onionmail.org].ndm448. Do not bulk-rename those files back to 1.jpg or 2.png. Do not strip [2AF20FA3]. Do not strip [thomasandersen70@onionmail.org]. Do not strip .ndm448. Stripping the extra ending is not a repair. It can make a later trusted tool worse, not better. The original name is already sitting in front of the tagged ending. You do not need to edit it to know what you lost.

Keep +README-WARNING+.txt with the locked files. Do not “clean up” every copy of the note. Do not fill in a wallet so the flyer looks complete. Do not invent a Session handle. Do not invent a leak blog. The printed contacts are part of how you prove this was this strain and not a different locker that only sounds similar. Keep the contact marks as identifiers: thomasandersen70@onionmail.org, the qTox ID 40E320AC41C066E58264ABF8A6B47A93F69DE2BE30FF94AE701EE15ED856FF5BB76A6B2068A4, the Dear Management opening, the 12-hour mail fuse, the 4-day leak clock, and the 7-day sample clock. Those artifacts are evidence. They are not instructions you should carry out.

Do not email that inbox. Do not add that qTox. Do not ask a friend to write them “just to see.” A calm address is still the people who locked the files. If a later message quotes +README-WARNING+.txt and offers “the real wallet,” that is still the same shop. If a later message skips the original inbox and asks for coin over a different address, that is still the same shop, or a copycat standing in the same doorway. If a later message says the family is definitely Makop, or definitely Phobos, and that you must pick one to proceed, they are selling a label. Keep both labels in the record. Do not pick one for a stranger.

Do not pay. There is no printed $ figure to “match.” A 12-hour silence rule is still a ransom. A 4-day leak claim is still a ransom. A 7-day sample threat is still a ransom. If someone claims they can already decrypt Ndm448 files for a fee because they can recite Dear Management and the qTox ID, they are selling a report, not a key. If they mention thomasandersen70@onionmail.org as proof they “already called the crew,” they read the same note you did. Do not answer. Do not complete their checkout. Do not help them fix the flyer.

If Windows still offers to pick an app for the .ndm448 type, decline it. There is no player for that ending.

The Bottom Line

Ndm448 ransomware is a locker with a tagged filename, a warning note that greets Management, and a checkout that names an inbox and a qTox ID. It keeps the old name and appends a victim ID, thomasandersen70@onionmail.org, and .ndm448. 1.jpg becomes 1.jpg.[2AF20FA3].[thomasandersen70@onionmail.org].ndm448. 2.png becomes 2.png.[2AF20FA3].[thomasandersen70@onionmail.org].ndm448. The note is +README-WARNING+.txt. It claims a leak, points you at that inbox, prints a 12-hour qTox fallback with ID 40E320AC41C066E58264ABF8A6B47A93F69DE2BE30FF94AE701EE15ED856FF5BB76A6B2068A4, forbids renaming and restarts, prints a 4-day leak clock and a 7-day sample clock, and never prints a $ figure, a wallet, a Session ID, or a leak blog. Some writeups say Makop. Public detections say Phobos. This page reports both. There is no public free decryptor known for this strain.

Do not pay. Do not email thomasandersen70@onionmail.org. Do not add that qTox. Do not rename the pile in bulk. Keep +README-WARNING+.txt and a .ndm448 sample. If you take one sentence with you, take this. A folder of names ending in [ID].[thomasandersen70@onionmail.org].ndm448, plus +README-WARNING+.txt with that inbox and that qTox ID, is ransomware on the first sighting. Treat it that way before anyone offers to fill the $ line the flyer left empty, or to pick Makop or Phobos for you.