AI Risk Wire

Cases › other › LR-2026-0427

Shareholders accuse Ostin Technology of deepfake-driven pump-and-dump scheme

Preliminary Why: Publisher not yet named · subject to change

Developing: a major or severe case captured in the last 72 hours. Later changes are logged on the corrections page.

Status: no action reported

Severity major
Reported 17 Feb 2026

No source states: loss or records, developer and model, agent tool, could do, deployer, industry.

Severity major: Test: a regulator involved (FBI, SEC Office of Inspector General, FINRA referral) and two or more affected parties stated (more than 235 alleged victims).

According to a lawsuit filed in the Southern District of New York, AI-generated deepfake videos, stolen advisor credentials and fake promotion were allegedly used in a pump-and-dump scheme around Ostin Technology Group's NASDAQ-listed shares. The plaintiffs allege that fake social media profiles borrowed the names and credentials of real advisors, and that promoters in WhatsApp groups issued daily buying instructions. The share price rose from $0.78 to $9.40 between mid-April and late June 2025, then fell to $0.55 in a single session on June 26, 2025, and stop-loss orders reportedly failed to trigger. The Department of Justice later unsealed a criminal indictment against two individuals, and NASDAQ halted trading in the shares. No determination on the merits has been made, and the case remains at an early stage.

What happened

1 · What it reached or didThe plaintiffs say they are in contact with more than 235 alleged victims, with individual losses ranging from around $10,000 to over $820,000.
2 · How it was caughtAn investigation led by the FBI and the SEC Office of Inspector General, with a FINRA referral, led NASDAQ to halt trading of OST shares indefinitely.

What was done

No source states an action or fix.

Risks

Read from the sources; not yet reviewed by a person.

Controls

Not yet read for controls. Controls that mitigate the primary risk:

Model

Marking machine-made output · Abuse monitoring and account enforcement · Content safety classifiers

Application

People told they are dealing with AI

Infrastructure / target

Phishing and fraud filters

Evidence

No source states: what the AI was doing, what went wrong, when it happened, when it was found, how many records were exposed, any court case, the cause, what was done.

Show the full account: 8 items from the primary sources

What happened, in order

  1. late 2024 Plaintiffs say the alleged scheme's groundwork began.
  2. mid-April to late June 2025 OST share price rose from $0.78 to $9.40 during this period.
  3. around May 11, 2025 Alleged coordinated promotional blitz launched using fake social media profiles.
  4. September 2025 Department of Justice unsealed a criminal indictment.
  5. February 16 Shareholders filed the lawsuit in the Southern District of New York.
  6. July 4 Retail investors were allegedly told to hold until this date.

Not dated in the sources:

  • Stop-loss orders reportedly failed to trigger during the single-session drop.
  • NASDAQ halted trading of OST shares indefinitely.
Show every field, with its source and grade

What happened

Earliest source we hold
2026-02-17
D inferred by us from the described behaviour, reason shown
What set it off
misused by a person
C one secondary source states it
Who caused it
an insider
C one secondary source states it
What went wrong
other
D inferred by us from the described behaviour, reason shown
primary risk
RK19
D inferred by us from the described behaviour, reason shown
secondary risks
RK03
D inferred by us from the described behaviour, reason shown

Impact

Severity
major
D inferred by us from the described behaviour, reason shown
Kind of harm
money
C one secondary source states it
Who was affected
More than 235 alleged victims, per the plaintiffs
C one secondary source states it
Why this severity
Test: a regulator involved (FBI, SEC Office of Inspector General, FINRA referral) and two or more affected parties stated (more than 235 alleged victims).
D inferred by us from the described behaviour, reason shown

Notes on gaps

No remediations are reported.

LR-2026-0427 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON