WordPress Publishes AI Guidelines To Combat AI Slop

  • Quality standards do not change with AI
  • Encourages responsible use of AI
  • Low-effort or unverified AI output is explicitly discouraged

WordPress published new AI guidelines to encourage responsible use of AI and ensure that GPL licensing obligations are met.

WordPress published guidelines for using AI for coding plugins, themes, documentation, and media assets. The purpose of the guidelines, guided by five principles, is to keep WordPress contributions transparent, GPL-compatible, and human-accountable, while maintaining high quality standards for AI-assisted work.

The new guidelines lists the following five principles:

  1. “You are responsible for your contributions (AI can assist, but it isn’t a contributor).
  2. Disclose meaningful AI assistance in your PR description and/or Trac ticket comment.
  3. License compatibility matters: contributions must remain compatible with GPLv2-or-later, including AI-assisted output.
  4. Non-code assets count too (docs, screenshots, images, educational materials).
  5. Quality over volume: avoid low-signal, unverified “AI slop”; reviewers may close or reject work that doesn’t meet the bar.”

Transparency

The purpose of the transparency guidelines is to encourage contributors to disclose that AI was used and how it was used so that reviewers can be aware when evaluating the work.

License Compatibility And Tool Choice

Licensing is a big deal with WordPress because it’s designed to be a fully open source publishing platform under the GPLv2 licensing framework. Everything that’s made for WordPress, including plugins and themes, must also be open source. It’s an essential element of everything created with WordPress.

The guidelines specify that AI cannot be used if the output is not licensable under GPLv2.

It also states:

“Do not use tools whose terms forbid using their output in GPL-licensed projects or impose additional restrictions on redistribution.

Do not rely on tools to “launder” incompatible licenses. If an AI output reproduces non-free or incompatible code, it cannot be included.”

AI Slop

Of course, the guidelines address the issue of AI slop. In this case, AI slop is defined as hallucinated references (such as links or APIs that do not exist), overly complicated code where simpler solutions exist, and GitHub PRs that are generic or do not reflect actual testing or experience.

The AI Slop guidelines has recommendations of what they expect from contributors:

“Use AI to draft, then review yourself.

Submit PRs (or patches) that are small, concise and with atomic and well defined commit messages to make reviewing easier.

Run and document real tests.

Link to real Trac tickets, GitHub issues, or documentation that you have verified.”

The guidelines are clear that the WordPress contributors who are responsible for overseeing, reviewing, and deciding whether changes are accepted into a specific part of the project may close or reject contributions that they determine to be AI slop “with little added human insight.”

Takeaways

The new WordPress AI guidelines appear to be about preserving trust in the contribution process as AI becomes more common across development, documentation, and media creation. It in no way discourages the use of AI but rather encourages its use in a responsible manner.

Requiring disclosure, enforcing GPL compatibility, and giving maintainers the authority to reject low-quality submissions, the guidelines set boundaries that protect both the legal integrity of the WordPress project and the time of its reviewers.

Source: https://www.searchenginejournal.com/wordpress-ai-guidelines/566442/

2024 Wordfence Vulnerability Year in Review

Highlights from the Wordfence 2024 WordPress Security Report

  • Vulnerabilities disclosed in 2024 increased by 68% from 2023.
  • 81% of vulnerabilities disclosed in 2024 had a ‘Medium’ severity CVSS score.
  • Contributor-level access was the most common access requirement to exploit vulnerabilities in 2024, accounting for 34% of all vulnerabilities disclosed.
  • Approximately 35% of all vulnerabilities disclosed in 2024 remain unpatched in 2025.
  • 58% of all vulnerabilities disclosed in 2024 were in software with fewer than 10,000 active installations, and 19% of all vulnerabilities disclosed were in software with 50,000 active installations or more. 
  • Cross-Site Scripting vulnerabilities were the #1 vulnerability type disclosed in 2024, with Contributor-level Cross-Site Scripting vulnerabilities accounting for 56% of that total. 
    • Only around 5.7% of Cross-Site Scripting vulnerabilities had minimal authentication requirements and no user interaction requirements to exploit. 
    • 23% of all Cross-Site Scripting vulnerabilities from 2024 were Reflected Cross-Site Scripting.

  • Cross-Site Request Forgery vulnerabilities are on a comparative decline from previous years.  
  • 7.4% of all vulnerabilities disclosed in 2024 were considered high-threat (i.e. likely to be exploited with a damaging impact). This was a 149% increase from the number of high-threat issues disclosed in 2023. Arbitrary File Uploads were the most common vulnerability type disclosed in this category, with Privilege Escalation in second place. 
  • Over 68% of all vulnerabilities disclosed are considered low-risk to most WordPress site owners based on authentication level or user interaction requirements to exploit.  
  • Plugin vulnerabilities remain the biggest software threat to WordPress, accounting for 96% of all vulnerabilities disclosed.

  • Wordfence blocked and logged over 54 billion malicious requests, and blocked over 55 billion password attacks in 2024. 
  • Cross-Site Scripting exploit attempts were the number one blocked with 9 billion requests blocked in 2024, and SQL Injection was next with 1.1 billion requests blocked. 
  • LiteSpeed Cache <= 6.3.0.1 – Unauthenticated Privilege Escalation vulnerability was the number one targeted vulnerability in 2024 based on our custom firewall rules. This is likely due to the brute force requirements to successfully exploit and the fact that it is an attractive target.  
  • Password attacks overall are on the decline and exploits targeting software vulnerabilities are on the incline as of the end of 2024. 

Key Takeaways and Recommendations for 2025

  • Expect the trend of increased vulnerability disclosures to continue through 2025 as bug bounty programs and CNA roles continue to drive more research. While the sheer number may seem daunting, the majority remain low-risk if proper defenses (such as WAFs, continuous monitoring, and prompt patching) are in place.
  • Developers need to establish clear methods of communication for responsible disclosure as the number of vulnerabilities reported continues to rise. 
  • Layered security and defense in depth is going to be critical for WordPress site owners security through 2025 and beyond.
  • Threat actors are shifting attack techniques on WordPress, likely due to an overall improved posture of software security in the WordPress ecosystem as a result of more responsible disclosure and general security awareness from site owners.   
  • Security education and awareness will be crucial to continue growth and continue improving the posture of security in WordPress through 2025 and beyond.
  • Site owners need to proactively protect their sites by following security best practices and utilizing various security tools like a Web Application Firewall, Malware Scanner, Vulnerability Scanner, 2-Factor Authentication, and more. 
  • Removing unused and abandoned WordPress plugins and themes may be critically important in 2025 and beyond.

Read the full report: https://www.wordfence.com/wp-content/uploads/2025/04/2024-Annual-WordPress-Security-Report-by-Wordfence.pdf

A Win for Encryption: France Rejects Backdoor Mandate

In a moment of clarity after initially moving forward a deeply flawed piece of legislation, the French National Assembly has done the right thing: it rejected a dangerous proposal that would have gutted end-to-end encryption in the name of fighting drug trafficking. Despite heavy pressure from the Interior Ministry, lawmakers voted Thursday night (article in French) to strike down a provision that would have forced messaging platforms like Signal and WhatsApp to allow hidden access to private conversations.

The vote is a victory for digital rights, for privacy and security, and for common sense.

The proposed law was a surveillance wishlist disguised as anti-drug legislation. Tucked into its text was a resurrection of the widely discredited “ghost” participant model—a backdoor that pretends not to be one. Under this scheme, law enforcement could silently join encrypted chats, undermining the very idea of private communication. Security experts have condemned the approach, warning it would introduce systemic vulnerabilities, damage trust in secure communication platforms, and create tools ripe for abuse.

The French lawmakers who voted this provision down deserve credit. They listened—not only to French digital rights organizations and technologists, but also to basic principles of cybersecurity and civil liberties. They understood that encryption protects everyone, not just activists and dissidents, but also journalists, medical professionals, abuse survivors, and ordinary citizens trying to live private lives in an increasingly surveilled world.

A Global Signal

France’s rejection of the backdoor provision should send a message to legislatures around the world: you don’t have to sacrifice fundamental rights in the name of public safety. Encryption is not the enemy of justice; it’s a tool that supports our fundamental human rights, including the right to have a private conversation. It is a pillar of modern democracy and cybersecurity.

As governments in the U.S., U.K., Australia, and elsewhere continue to flirt with anti-encryption laws, this decision should serve as a model—and a warning. Undermining encryption doesn’t make society safer. It makes everyone more vulnerable.

This victory was not inevitable. It came after sustained public pressure, expert input, and tireless advocacy from civil society. It shows that pushing back works. But for the foreseeable future, misguided lobbyists for police national security agencies will continue to push similar proposals—perhaps repackaged, or rushed through quieter legislative moments.

Supporters of privacy should celebrate this win today. Tomorrow, we will continue to keep watch.

Source: https://www.eff.org/deeplinks/2025/03/win-encryption-france-rejects-backdoor-mandate

Cloudflare turns AI against itself with endless maze of irrelevant facts

On Wednesday, web infrastructure provider Cloudflare announced a new feature called “AI Labyrinth” that aims to combat unauthorized AI data scraping by serving fake AI-generated content to bots. The tool will attempt to thwart AI companies that crawl websites without permission to collect training data for large language models that power AI assistants like ChatGPT.

Cloudflare, founded in 2009, is probably best known as a company that provides infrastructure and security services for websites, particularly protection against distributed denial-of-service (DDoS) attacks and other malicious traffic.

Instead of simply blocking bots, Cloudflare’s new system lures them into a “maze” of realistic-looking but irrelevant pages, wasting the crawler’s computing resources. The approach is a notable shift from the standard block-and-defend strategy used by most website protection services. Cloudflare says blocking bots sometimes backfires because it alerts the crawler’s operators that they’ve been detected.

“When we detect unauthorized crawling, rather than blocking the request, we will link to a series of AI-generated pages that are convincing enough to entice a crawler to traverse them,” writes Cloudflare. “But while real looking, this content is not actually the content of the site we are protecting, so the crawler wastes time and resources.”

The company says the content served to bots is deliberately irrelevant to the website being crawled, but it is carefully sourced or generated using real scientific facts—such as neutral information about biology, physics, or mathematics—to avoid spreading misinformation (whether this approach effectively prevents misinformation, however, remains unproven). Cloudflare creates this content using its Workers AI service, a commercial platform that runs AI tasks.

Cloudflare designed the trap pages and links to remain invisible and inaccessible to regular visitors, so people browsing the web don’t run into them by accident.

A smarter honeypot

AI Labyrinth functions as what Cloudflare calls a “next-generation honeypot.” Traditional honeypots are invisible links that human visitors can’t see but bots parsing HTML code might follow. But Cloudflare says modern bots have become adept at spotting these simple traps, necessitating more sophisticated deception. The false links contain appropriate meta directives to prevent search engine indexing while remaining attractive to data-scraping bots.

“No real human would go four links deep into a maze of AI-generated nonsense,” Cloudflare explains. “Any visitor that does is very likely to be a bot, so this gives us a brand-new tool to identify and fingerprint bad bots.”

This identification feeds into a machine-learning feedback loop—data gathered from AI Labyrinth is used to continuously enhance bot detection across Cloudflare’s network, improving customer protection over time. Customers on any Cloudflare plan—even the free tier—can enable the feature with a single toggle in their dashboard settings.

A growing problem

Cloudflare’s AI Labyrinth joins a growing field of tools designed to counter aggressive AI web crawling. In January, we reported on “Nepenthes,” software that similarly lures AI crawlers into mazes of fake content. Both approaches share the core concept of wasting crawler resources rather than simply blocking them. However, while Nepenthes’ anonymous creator described it as “aggressive malware” meant to trap bots for months, Cloudflare positions its tool as a legitimate security feature that can be enabled easily on its commercial service.

The scale of AI crawling on the web appears substantial, according to Cloudflare’s data that lines up with anecdotal reports we’ve heard from sources. The company says that AI crawlers generate more than 50 billion requests to their network daily, amounting to nearly 1 percent of all web traffic they process. Many of these crawlers collect website data to train large language models without permission from site owners, a practice that has sparked numerous lawsuits from content creators and publishers.

The technique represents an interesting defensive application of AI, protecting website owners and creators rather than threatening their intellectual property. However, it’s unclear how quickly AI crawlers might adapt to detect and avoid such traps, potentially forcing Cloudflare to increase the complexity of its deception tactics. Also, wasting AI company resources might not please people who are critical of the perceived energy and environmental costs of running AI models.

Cloudflare describes this as just “the first iteration” of using AI defensively against bots. Future plans include making the fake content harder to detect and integrating the fake pages more seamlessly into website structures. The cat-and-mouse game between websites and data scrapers continues, with AI now being used on both sides of the battle.

Source: https://arstechnica.com/ai/2025/03/cloudflare-turns-ai-against-itself-with-endless-maze-of-irrelevant-facts/

See also: https://techcrunch.com/2025/03/27/open-source-devs-are-fighting-ai-crawlers-with-cleverness-and-vengeance/ and https://www.theregister.com/2025/03/21/cloudflare_ai_labyrinth/

FBI seizes Cracked.io, Nulled.to hacking forums in Operation Talent

Update January 29, 14:15 EST: Seizure banners were added to the cracked[.]io, cracked[.]to, nulled [.]to, starkrdp[.]io, mysellix[.]io, and sellix[.]io, confirming that the domains had been seized in a joint law enforcement action dubbed “Operation Talent” that included authorities from the United States, Italy, Spain, Europe, France, Greece, Australia, and Romania.

“This website, as well as the information on the customers and victims of the website, has been seized by international law enforcement partners,” the banners read.

Cracked.io’s staff has released a new statement on Telegram confirming that law enforcement has seized the cracked.io domain.

“Now that everyone has more clarity on the situation, Cracked.io has been seized under operation talent with specific reasons being undisclosed,” they said.

“We are still waiting for the official court documentation from the data centre and the domain host. We will inform you guys further on those details once we have it. A sad day indeed for our community.”

Update January 29th 16:54 EST: Europol said that an operation is currently undergoing and more information will be available at a later date.


Original story below

The FBI has seized the domains for the infamous Cracked.io and Nulled.to hacking forums, which are known for their focus on cybercrime, password theft, cracking, and credential stuffing attacks.

While some of their members also engaged in ethical hacking discussions, the sites were widely regarded as a hub for cybercriminal activity.

They also hosted content related to software cracks, hacking tools like “configs” used by credential stuffing attack tools (e.g., OpenBullet and SilverBullet), and other illicit activities, including a “combo lists” marketplace with stolen credentials or databases.

When trying to open the sites, web browsers display “Error 1000. DNS points to prohibited IP” and Error 1016. Origin DNS error” messages.

Today, the FBI seized the forums’ domains and changed their name servers to ns1.fbi.seized.gov and ns2.fbi.seized.gov from their previous Cloudflare name servers.

Cracked.io’s staff published an announcement on their Telegram channel earlier today, blaming a data center issue for the ongoing access problems.

“There is an active issue in our data centre which the staff is working on. Hence services remain offline till the issue is resolved. We will get detailed report later,” they said.

“We can only hope it is resolved without further issue. No estimated time at this moment. The current status from data centre is that it may take up to 1 day.”

Today, the FBI also seized domains used by:

  • MySellIX (mysellix.io) and SellIX (sellix.io), two platforms that allowed users to create their own online stores, which threat actors also used to sell stolen data, software keys, and compromised accounts, and
  • StarkRDP (starkrdp.io), a Windows RDP virtual hosting provider that some threat actors allegedly used for credential stuffing attacks.

An FBI spokesperson was not immediately available for comment when contacted by BleepingComputer earlier today.

While the law enforcement agency has yet to share more information about this wave of seizures, all signs point to a crackdown on platforms involved in credential stuffing and stolen account credentials.

Source: https://www.bleepingcomputer.com/news/security/fbi-seizes-crackedio-nulledto-hacking-forums-in-operation-talent/

FTC orders GoDaddy to fix poor web hosting security practices

See also:
GoDaddy slapped with wet lettuce for years of lax security and ‘several major breaches’

The Federal Trade Commission (FTC) will require web hosting giant GoDaddy to implement basic security protections, including HTTPS APIs and mandatory multi-factor authentication, to settle charges that it failed to secure its hosting services against attacks since 2018.

FTC says the Arizona-based company’s claims of reasonable security practices also misled millions of web-hosting customers because GoDaddy was instead “blind to vulnerabilities and threats in its hosting environment” due to its failings to implement standard security tools and practices.

“Millions of companies, particularly small businesses, rely on web hosting providers like GoDaddy to secure the websites that they and their customers rely on,” said Samuel Levine, Director of the FTC’s Bureau of Consumer Protection.

“The FTC is acting today to ensure that companies like GoDaddy bolster their security systems to protect consumers around the globe.”

According to the FTC’s complaint, GoDaddy’s unreasonable security practices included failing to use multi-factor authentication (MFA), manage software updates, log security-related events, segment its network, monitor for security threats (including by failing to use software that could actively detect threats from its many logs), and use file integrity monitoring.

The company also failed to inventory and manage assets, assess risks to its website hosting services, and secure connections to services that provide access to consumer data.

Lax security practices led to multiple breaches

The FTC says that, between 2019 and 2022, these data security failures led to several major security breaches, resulting in threat actors gaining access to customers’ websites and data.

For instance, in February 2023, the hosting giant disclosed that unknown attackers stole source code and installed malware on compromised servers after breaching its cPanel shared hosting environment in a multi-year breach.

The company said it only discovered the breach in early December 2022 after receiving customer complaints that their websites were being used to redirect to unknown domains.

GoDaddy also revealed at the time that security breaches disclosed in November 2021 and March 2020 were also linked to this campaign.

The November 2021 breach affected 1.2 million Managed WordPress customers. Attackers hacked into GoDaddy’s hosting environment using a compromised password and obtained email addresses, WordPress Admin passwords, sFTP and database credentials, and SSL private keys from some clients.

Following the March 2020 breach, GoDaddy notified 28,000 customers that an attacker used their web hosting credentials to connect via SSH in October 2019.

Mandatory MFA for employees and customers

According to a proposed settlement order, the FTC will require GoDaddy to establish a robust information security program and prohibits the company from misleading customers about its security protections. The order also mandates that GoDaddy hire an independent third-party assessor to conduct biennial reviews of its information security program.

The company is also required to add mandatory MFA for all customers, employees, and contractors’ staff “to any Hosting Service supporting tool or asset, including connecting to any database” and “at least one method that does not require the customer to provide a telephone number, such as by integrating authentication applications or allowing the use of security key.”

In December, the FTC also ordered Marriott International and Starwood Hotels to implement a robust data security program following failures that led to massive data breaches in 2014 and 2018, exposing over 340 million guest records.

Marriott settled with the FTC in October 2014 and agreed to pay $52 million to 49 states to resolve claims related to these data breaches.

Update January 17, 08:28 EST: GoDaddy sent the following statement after the article was published:

GoDaddy has a long history of offering innovative products to our web hosting customers. We are focused on protecting our customers’ data and websites, and we invest significant resources in technologies, tools and talent to help safeguard systems and information. We are constantly improving our security capabilities and have already implemented a number of the requirements in the settlement agreement with the FTC. Notably, the resolution of this matter includes no admission of fault and no monetary penalties. We expect minimal financial impact associated with complying with the terms of the agreement with the FTC. We plan to continue to invest in our defenses to address evolving threats and help keep our customers, their websites and their data safe.

Source: https://www.bleepingcomputer.com/news/security/ftc-orders-godaddy-to-fix-poor-web-hosting-security-practices/

See also:
GoDaddy slapped with wet lettuce for years of lax security and ‘several major breaches’

Justice Department and FBI Conduct International Operation to Delete Malware Used by China-Backed Hackers

Court-Authorized Operation Removes PlugX Malware from Over 4,200 Infected U.S. Computers

The Justice Department and FBI today announced a multi-month law enforcement operation that, alongside international partners, deleted “PlugX” malware from thousands of infected computers worldwide. As described in court documents unsealed in the Eastern District of Pennsylvania, a group of hackers sponsored by the People’s Republic of China (PRC), known to the private sector as “Mustang Panda” and “Twill Typhoon,” used a version of PlugX malware to infect, control, and steal information from victim computers.

According to court documents, the PRC government paid the Mustang Panda group to, among other computer intrusion services, develop this specific version of PlugX. Since at least 2014, Mustang Panda hackers then infiltrated thousands of computer systems in campaigns targeting U.S. victims, as well as European and Asian governments and businesses, and Chinese dissident groups. Despite previous cybersecurity reports, owners of computers still infected with PlugX are typically unaware of the infection. The court-authorized operation announced today remediated U.S.-based computers infected with Mustang Panda’s version of PlugX.    

“The Department of Justice prioritizes proactively disrupting cyber threats to protect U.S. victims from harm, even as we work to arrest and prosecute the perpetrators,” said Assistant Attorney General Matthew G. Olsen of the Justice Department’s National Security Division. “This operation, like other recent technical operations against Chinese and Russian hacking groups like Volt Typhoon, Flax Typhoon, and APT28, has depended on strong partnerships to successfully counter malicious cyber activity. I commend partners in the French government and private sector for spearheading this international operation to defend global cybersecurity.”

“Leveraging our partnership with French law enforcement, the FBI acted to protect U.S. computers from further compromise by PRC state-sponsored hackers,” said Assistant Director Bryan Vorndran of the FBI’s Cyber Division. “Today’s announcement reaffirms the FBI’s dedication to protecting the American people by using its full range of legal authorities and technical expertise to counter nation-state cyber threats.”

“This wide-ranging hack and long-term infection of thousands of Windows-based computers, including many home computers in the United States, demonstrates the recklessness and aggressiveness of PRC state-sponsored hackers,” said U.S. Attorney Jacqueline Romero for the Eastern District of Pennsylvania. “Working alongside both international and private sector partners, the Department of Justice’s court-authorized operation to delete PlugX malware proves its commitment to a ‘whole-of-society’ approach to protecting U.S. cybersecurity.”

“The FBI worked to identify thousands of infected U.S. computers and delete the PRC malware on them. The scope of this technical operation demonstrates the FBI’s resolve to pursue PRC adversaries no matter where they victimize Americans,” said Special Agent in Charge Wayne Jacobs of the FBI Philadelphia Field Office.

The international operation was led by French law enforcement and Sekoia.io, a France-based private cybersecurity company, which had identified and reported on the capability to send commands to delete the PlugX version from infected devices. Working with these partners, the FBI tested the commands, confirmed their effectiveness, and determined that they did not otherwise impact the legitimate functions of, or collect content information from, infected computers. In August 2024, the Justice Department and FBI obtained the first of nine warrants in the Eastern District of Pennsylvania authorizing the deletion of PlugX from U.S.-based computers. The last of these warrants expired on Jan. 3, 2025, thereby concluding the U.S. portions of the operation. In total, this court-authorized operation deleted PlugX malware from approximately 4,258 U.S.-based computers and networks.

The FBI, through the victims’ internet service providers, is providing notice to U.S. owners of Windows-based computers affected by this court-authorized operation.

The FBI’s Philadelphia Field Office and Cyber Division, the U.S. Attorney’s Office for the Eastern District of Pennsylvania, and the National Security Cyber Section of Justice Department’s National Security Division led the domestic disruption operation. This operation would not have been successful without the valuable collaboration of to the Cyber Division of the Paris Prosecution Office, French Gendarmerie Cyber Unit C3N, and Sekoia.io.

The FBI continues to investigate Mustang Panda’s computer intrusion activity. If you believe you have a compromised computer or device, please visit the FBI’s Internet Crime Complaint Center (IC3). You may also contact your local FBI field office directly. The FBI strongly encourages the use of anti-virus software as well as the application of software security updates to help prevent reinfection.

Source: https://www.justice.gov/opa/pr/justice-department-and-fbi-conduct-international-operation-delete-malware-used-china-backed

Criminals Keep Hacking Themselves, Letting Researchers Unmask Them

Infostealer malware is often hidden in pirated or cracked software, and hackers then post the harvested credentials and other data online. Criminals have been infected too.

Cybersecurity researchers are increasingly unmasking or finding new information on suspected criminals from a rich and unlikely source: the tsunami of compromised credentials, browser profiles, and other system information available on Telegram. In other words, criminals are accidentally hacking themselves, perhaps by downloading cracked software laden with malware, which is then exposing their identities to researchers, and potentially law enforcement too.

In the latest example, cybersecurity firm Hudson Rock said last week it had uncovered information on Mujtaba Raza and Mohsin Raza, two alleged fraudsters on the FBI’s Most Wanted list. In April 2021, U.S. authorities charged the two men with conspiracy to produce and transfer in false identification documents, three counts of transferring false identification documents, false use of a passport, and aggravated identity theft. The men allegedly ran an illegal e-commerce business out of Karachi, Pakistan, called SecondEye Solution. This company sold digital images of fake passports, driver’s licenses, and national identity cards for more than 200 countries and territories, and the men advertised the company’s services on at least one hacker forum, according to the DOJ’s press release at the time. The DOJ said that a member of the Internet Research Agency LLC, the Russian social media and election interference organization, bought multiple fake identity documents from SecondEye.

Since those charges, Mujtaba and Mohsin have been fugitives.

Now using data from infostealers, which are a class of malware that harvest credentials and other data from an infected computer, Hudson Rock said it had identified two computers that it believes contained data related to the pair. Various pieces of infostealer malware exist, with names such as RedLine, Raccoon, Mars, BlackGuard, and Erbium. These are spread to victims by fake ExpressVPN applications, cryptocurrency wallets, or cracked or pirated software. Once the malware administrators have harvested credentials, they often sell them to other cybercriminals before posting them for free on Telegram. It’s typically here that researchers can collect the exposed credentials and then warn impacted companies. 

Included in the infostealer logs Hudson Rock found were credentials for SecondEye email accounts; cloud storage accounts linked to the same email addresses; and others for Forwarderz, another associated company.

The data harvested by the infostealers and then reviewed by Hudson Rock included much more than just passwords stored on the computers, though. Hudson Rock says it included the “entire browsing history” from one of the machines; auto-fill data, such as addresses, account numbers, and passport numbers; as well as information on when the computer was hacked, its name, and its related IP address. When one of the computers was initially infected, the malware took a screenshot. It shows a Forwarderz-branded Skype account being used, according to Hudson Rock.

Hudson Rock believes the two compromised computers don’t belong to Mujtaba and Mohsin themselves, but two other associates. Facebook and Github profiles linked to the machines, as well as a physical address included in the data, pointed to two men called Muhammad Qamber and Bakhtawar Abbas. Neither man responded to a request for comment from 404 Media.

Infostealer credentials are responsible for the recent wave of Snowflake breaches, in which hackers accessed data from a series of high profile companies, including AT&T and Ticketmaster.

Hudson Rock’s blog post says it was “reviewed and approved by the Federal Bureau of Investigation (FBI), meeting all necessary guidelines for public disclosure.” The FBI did not respond to a request for comment. Neither did Hudson Rock.

In another case, in July researchers from cybersecurity firm RecordedFuture said they found 3,324 unique credentials used to access known child abuse imagery (CSAM) websites. That data also included those peoples’ usernames, IP addresses, and system information, which could let the researchers or law enforcement unmask the users’ real identities.

RecordedFuture said it “used the data contained in infostealer logs and open-source intelligence (OSINT) to identify two individuals and found further digital artifacts, including cryptocurrency addresses, belonging to a third individual.” RecordedFuture did not respond to a request for comment. 

Whether such information would be admissible in court is a separate question, however, and would in part depend on whether law enforcement consider credentials harvested from infostealer infections to be publicly available information. The FBI did not respond to a request for comment.

Source: https://www.404media.co/criminals-keep-hacking-themselves-letting-researchers-unmask-them/

PSA: Your Site Isn’t Hacked By This Bitcoin Scam, Keep the Money

On January 19th, 2023, a member of the Wordfence Threat Intelligence team received an email from their personal blog, claiming the site had been hacked, and we received two reports from Wordfence users who received the same message. The email claimed that the site had been hacked due to a vulnerability on the site. The email went on to demand about $3,000 worth of Bitcoin to prevent the malicious actor from damaging the site’s reputation. This is of course only a scare tactic, and not a true cause for concern. The site was not actually hacked.

This campaign appears to have begun on or around January 18, 2023, and while our data on it is light, the campaign is ongoing. The messages are being sent by a threat actor or a bot they control to submit the message through a contact form on a website. As we do not have data on emails submitted directly through a contact form, this attack campaign is likely to be significantly more prolific than the numbers we have available.

The message in question, which can be seen below in its email form, is a scare tactic that is used to trick victims into paying to prevent a leak of sensitive data, damage to the website, or whatever other potential consequences the vague threat may conjure up in the site owner’s mind.

From: Manie Hedin hacker@sludgepool.org
Subject: Your Site Has Been Hacked

Message Body:
Your Site Has Been Hacked

PLEASE FORWARD THIS EMAIL TO SOMEONE IN YOUR COMPANY WHO IS ALLOWED TO MAKE IMPORTANT DECISIONS!

We have hacked your website https://.com and extracted your databases.

How did this happen?

Our team has found a vulnerability within your site that we were able to exploit. After finding the vulnerability we were able to get your database credentials and extract your entire database and move the information to an offshore server.

What does this mean?

We will systematically go through a series of steps of totally damaging your reputation. First your database will be leaked or sold to the highest bidder which they will use with whatever their intentions are. Next if there are e-mails found they will be e-mailed that their information has been sold or leaked and your https://.com was at fault thusly damaging your reputation and having angry customers/associates with whatever angry customers/associates do. Lastly any links that you have indexed in the search engines will be de-indexed based off of blackhat techniques that we used in the past to de-index our targets.

How do I stop this?

We are willing to refrain from destroying your site’s reputation for a small fee. The current fee is $3000 in bitcoins (0.14 BTC).

The amount(approximately): $3000 (0.14 BTC)
The Address Part 1: bc1qe4xvhksgapl3p76mm
The Address Part 2: fz7thdnmkeuxry08kjhcn

So, you have to manually copy + paste Part1 and Part2 in one string made of 42 characters with no space between the parts that start with “b” and end with “n” is the actually address where you should send the money to.

Once you have paid we will automatically get informed that it was your payment. Please note that you have to make payment within 72 hours after receiving this message or the database leak, e-mails dispatched, and de-index of your site WILL start!

How do I get Bitcoins?

You can easily buy bitcoins via several websites or even offline from a Bitcoin-ATM.

What if I don’t pay?

If you decide not to pay, we will start the attack at the indicated date and uphold it until you do, there’s no counter measure to this, you will only end up wasting more money trying to find a solution. We will completely destroy your reputation amongst google and your customers.

This is not a hoax, do not reply to this email, don’t try to reason or negotiate, we will not read any replies. Once you have paid we will stop what we were doing and you will never hear from us again!

Please note that Bitcoin is anonymous and no one will find out that you have complied.

While this extortion campaign may not pose any real danger, it is still important to take website security seriously. WordPress core, themes, and plugins need to be updated with the latest security updates to patch known vulnerabilities. Even with everything updated, there may be vulnerabilities that are not publicly known and do not have an available patch. For this reason, a website security solution that includes a web application firewall (WAF) that can block common exploits, such as Wordfence, should be implemented.

Cyber Observables
While this extortion campaign is still in its early stages, there are some observables that can be used to identify and block these extortion attempts.

Email Address
hacker@sludgepool[.]org

Bitcoin Address
bc1qe4xvhksgapl3p76mmfz7thdnmkeuxry08kjhcn

IP Addresses
138.199.18.140
138.199.18.61
212.102.57.5
216.24.216.249
212.102.57.24

Conclusion
In this post, we discussed an emerging extortion campaign where emails are being sent to site owners through contact forms. This campaign does not pose an actual threat to the website, but serves as a reminder to keep websites updated and implement a website security solution.

Source: https://www.wordfence.com/blog/2023/01/psa-your-site-isnt-hacked-by-this-bitcoin-scam-keep-the-money/

Inside a scammers’ lair: Ukraine busts 40 in fake bank call-centre raid

It looks like the sort of meeting room you might find in startups all over the world: diffuse lighting from windows down one wall, alongside a giant poster cityscape of New York’s Brooklyn Bridge, with the Manhattan skyline towering behind it.

The difference in this case is that that the computer workstations around the room are there for a different sort of “entrepreneurial” venture, and the room is empty not because no one showed up for work, but because the “employees” were in the process of being arrested.

This picture comes from the Ukraine Cyber Police, who raided a fraudulent call center just before New Year, where they say the three founders of the scam, plus 37 “staff”, were busted for allegedly operating a large-scale banking fraud.

Playbook + gift of gab = scam
You’re probably familiar with the scamming script they’re said to have used, and you probably know friends or family who have been pestered by scammers of this sort.

Some of you may even have acquaintances who were ripped off this way, because these scammers are well versed in gaining the trust of their victims.

Typically, the scammers try to convince you that your bank account is under attack from fraudsters (technically, that part is true – the caller is the attacker), and patiently offer to help you “secure” your account and “recover” lost or at-risk funds.

The scammers aim to turn people’s general awareness of banking scams into an excuse, a reason, a playbook, if you like, for carrying out a scam of their own.

Simply put, they call up pretending to be an official from your own bank, using a variety of tricks to make you accept their fictitious credentials as bank staff, and then “advise” you to take a series of disastrous steps.

The scammers’ first job is to convince you that a hacker has already gained access to your account.

The crooks typically use a mix of threatening, scary and urgent language, combined with the sort of attentiveness that you probably wish more call centre staff would show.

Even if you decide to call them back (don’t do it – you’re only reconnecting to the person who just called you, which proves nothing!), you’ll almost certainly find the scammers more prompt and more helpful than you’ve experienced in a long time when calling a real support line…

…so we’re not surprised that this sort of caller makes some people feel comfortable enough to keep on listening, even if they didn’t believe a word at first.

If in doubt, don’t give it out
As you can imagine, once the crooks know you’re starting to believe their cover story, they’ll start to milk you for personal information, often by pretending that they can see it for themselves on the “banking screen” in front of them, yet somehow always coaxing you to say it out loud first.

At that point, of course, they do know the information you just let slip, and they’ll pretend to “confirm” it or to “double-check” it to keep up the pretence.

There are then many ways that the crooks can defraud you or drain your account.

Sometimes, they may simply convince you to login on a fake “security” site as they coach you through the process, including getting you to go through any 2FA (two-factor authentication) process.

The Ukrainian call centre that just got busted seems to have worked that way, with victims being “helpfully” guided through the process of “cancelling” transactions that, in fact, never happened in the first place [automated translation]:

[These scammers] called people in Kazakhstan, pretending to be employees of the security service of banks. These people were notified of suspicious transactions and told that alleged outsiders had gained access to their accounts. Under the guise of “cancelling” transactions, victims were persuaded to provide financial data.

After receiving such information, the perpetrators transferred the victims’ money to account under their own control. They also issued quick loans and appropriated the loan amount.

For the conspiracy, the participants used bank accounts located in offshore zones, and cryptocurrency wallets.

In this way, the criminals defrauded [about 18,000 people].

High and dry
In other scams – this approach, unfortunately, is widely reported in the UK – the crooks present you with a brand-new account number, based at the same bank, which they announce is your “replacement account”.

The idea is that you’re being provided with new account details in the same way that if you were to ask for a new credit card due to fraud, it too would have a brand new number, expiry date and so on.

The crooks then convince you to transfer the funds from your “old, hacked” account to this new one, leading you to believe that the account was created by the bank minutes ago, especially for the purpose of “protecting” you from an active attack.

Of course, this “new account” is just a regular account that was opened recently by accomplices of the crooks, perhaps using fraudulent documentation to pass the bank’s know-your-customer (KYC) process.

So, the account it is already directly under the control of the scammers, and the money will typically be whisked out of that “new” account even before you finish the call.

In cases like this, victims sometimes tragically find themselves left high and dry by their bank, which may claim that because they apparently willingly transferred the funds of their own accord, and properly identified themselves to the online banking system (for example by using 2FA), the funds have technically not been “stolen”, and the bank therefore has no liability.

  • What to do?
  • Never believe anyone who contacts you out of the blue and claims to be “helping” you with a fraud investigation. That person isn’t stopping a fraud, they are starting one.
  • Never use contact details given to you by the other person when cybersecurity is at stake. This cannot possibly prove anything, given that the details probably came from a scammer in the first place. All you get is a false sense of “security”.
  • Never rely on the Caller ID number that shows up on your phone. The number that appears can easily be faked. If the caller tells you to “check the number if you don’t believe them”, you can be sure they’re a scammer.
  • Never let yourself be talked into handing over personal information, especially not to “prove” your identity. After all, it’s the other person who should be proving themselves to you. Visit your bank in person if you possibly can; if you need to call or interact online, look for contact details printed on something you know you received directly from the bank, such as the back of your payment card or a recent statement.
  • Never transfer funds to another account on someone else’s say so. You bank will never call you to ask you to do this, so any call of this sort must be a scam. Worse still, you could find yourself liable for the transfer if you approve it yourself, even if you were tricked into doing so.
  • Look out for friends and family who may be vulnerable. These scammers don’t give up easily, and they can be consummate actors when playing the role of a helpful official. Make sure your friends and family know to hang up right away, and to contact you personally for advice, so they never give the scammers a chance to “vouch” for themselves.

Source: https://nakedsecurity.sophos.com/2023/01/03/inside-a-scammers-lair-ukraine-busts-40-in-fake-bank-call-centre-raid/