OpenAI banned likely China-origin accounts that used AI to research US persons and locations and to plan social-engineering tactics. The activity involved researching US persons and locations and included social-engineering tactics. As a result, those accounts were removed from OpenAI’s services.
OpenAI banned accounts that used AI to support romance scam workflows, including outreach, translation, victim engagement, and investment-fraud lures. The action involved banning the accounts themselves. This reduces the availability of AI-assisted services for scam operations and signals stricter enforcement against AI-enabled fraud.
OpenAI banned accounts linked to an influence operation dubbed “Trolling Stone,” which generated comments about an alleged Russian cult leader’s arrest in Argentina using AI.
The report says the accounts were linked to a previously unreported operation.
As a result, those accounts were removed, and the incident was brought to light as an example of AI-assisted influence activity tied to Russia.
OpenAI banned accounts linked to the Rybar network that appear to have originated in Russia and used AI to support multilingual influence activity across websites and social platforms. The article says the accounts were linked to the Rybar network. This results in those Rybar-linked accounts being removed from OpenAI services and their AI-enabled influence activity being disrupted.
OpenAI banned an account linked to a person associated with Chinese law enforcement after detecting AI use tied to influence activity and online harassment operations. The account was banned by OpenAI (date not specified in the article). As a result, access to the account was cut off as OpenAI acted against the planned influence and harassment activity.
Every AI story that matters,
in your inbox by 8am.
TLDRocket reads all relevant sources, removes duplicate coverage, and summarises the
day in two minutes. Follow companies and topics for alerts, or get the
briefing in Slack. Free, no spam, unsubscribe anytime.
Reading TLDRocket needs no cookies, and the readership counts we rely on come from
our own cookieless analytics. Google Analytics is the exception: it sets cookies and
reports to Google, so it stays switched off until you allow it. You can change your
mind any time from “Cookie settings” in the footer.
Strictly necessary
Session security and form protection (tldrocket-session,
XSRF-TOKEN, 2 hours). The site cannot work without them,
so they need no consent.
Always on
Google Analytics 4 (_ga,
_ga_<id>, up to 2 years). Measures which
stories and sections readers use. Google acts as a third-party processor and may
store the data outside the EU. No advertising, no profiling, no data sold.