Trapdex Subscribe

CampaignsPublisher / pipeline compromise

axios npm maintainer lured with a fake company and Teams call; plain-crypto-js RAT dropper

Do this now

  1. Brief maintainers on fake-meeting lures that end in 'install this update'
  2. Search lockfiles for plain-crypto-js and the two axios versions; reimage hosts that installed them
  3. Block the C2 domain and IP
  4. Require trusted publishing or 2FA-gated publish for high-impact packages

Indicators to check

Look for any of these on your machines or in your logs:

  • packageaxios@1.14.1
  • packageaxios@0.30.4
  • packageplain-crypto-js@4.2.1

CSVJSONAll 6 indicators

What happened

For about two weeks the lead axios maintainer was worked with a cloned company, a fake Slack workspace and a fake Teams meeting, which pushed a fake 'update' that was a RAT. The attacker then published axios 1.14.1 and 0.30.4, both adding a pre-staged typosquat dependency whose postinstall installs a cross-platform backdoor. npm removed the versions about three hours after publication.

  • npm
  • Slack
  • Microsoft Teams

Attack chain

  1. Lure

    Fake founder outreach, cloned Slack workspace and a Teams meeting pushing a fake update

    First seen

  2. Artifact

    axios@1.14.1, axios@0.30.4 and plain-crypto-js@4.2.1 (postinstall setup.js)

  3. Actor

    UNC1069, DPRK-nexus (attribution: Google GTIG; basis: WAVESHAPER.V2 malware lineage, C2 reached from a VPN node UNC1069 used before, and adjacent infrastructure)

  4. Infrastructure

    • C2 domain registered 30 Mar 2026
    • C2 IP

    Last seen

Indicators

CSVJSON

All values are defanged (how to read them).

TypeValueCopy
packageaxios@1.14.1
packageaxios@0.30.4
packageplain-crypto-js@4.2.1
domainsfrclak[.]com
ip142[.]11[.]206[.]73
sha25658401c195fe0a6204b42f5f90995ece5fab74ce7c69c67a24c61a057325af668

Confidence: Moderate

Strong evidence, not yet confirmed by our own analysis. See the confidence scale for what each level requires. The sources below are the evidence.

Sources

Notes

  • The first-seen date is month-level: the lure ran for about two weeks before 30 Mar 2026. Overlaps fake-interview-style tradecraft; filed under publisher-pipeline because the outcome was a hijacked release.

Corrections

No corrections.

See the corrections policy. Spotted an error? Tell us.