Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@picsart/ai-sdknpm

@picsart/ai-sdk is a confirmed malicious npm package (MAL-2026-11781) that steals credentials and exfiltrates sensitive data (malicious version 3.32.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @picsart/ai-sdk (npm)

MAL-2026-11781
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @picsart/ai-sdk

What this malware does

npm/@picsart/ai-sdk is affected by the large-scale, self-propagating npm supply-chain worm of 2026-08-04 (the "Shai-Hulud: Here We Go Again" wave) — the same campaign that began with the compromise of the keyv and cacheable maintainer account. The listed version(s) were trojanized and republished by the worm after it reached an npm publish token belonging to a maintainer in this namespace; the payload enumerates every package a stolen token controls and republishes each with the same hook, so many packages under this scope were poisoned in the same short window. Every poisoned release adds a preinstall hook ("preinstall": "node setup.mjs") that runs on a bare npm install, before any project code. setup.mjs downloads a standalone Bun runtime and runs a byte-identical, heavily obfuscated ~728 KB second-stage credential stealer (shipped as Math_Symbol.js / math_init.js). It harvests GitHub, npm, AWS, GCP, Azure, HashiCorp Vault and Kubernetes credentials plus generic secrets and private keys (TruffleHog-style sweep), reads CI/CD secrets and identifies build runners, then republishes further packages the stolen token can reach. Rather than a fixed command-and-control host, it exfiltrates stolen findings to attacker-created GitHub repositories (descriptions reading "Shai-Hulud: Here We Go Again") and over DNS. Treat any environment that installed an affected version (with install scripts enabled) as compromised: rotate and revoke all reachable credentials (npm and GitHub tokens, cloud keys, Vault/Kubernetes secrets, and CI org/repo secrets). Part of the August 2026 npm worm that poisoned 400+ packages across many organizations.

The package advertises itself as a type-safe AI SDK library with main=./index.js and a single runtime dependency (fflate), but its declared preinstall hook (node setup.mjs) downloads the Bun runtime binary from https://github.com/oven-sh/bun/releases/download/bun-v1.3.13/ into a temp directory, chmod +x's it, and uses it to execFileSync a bundled sibling file math_init.js on every install. math_init.js is a 727KB Bun-CJS bundle (// @bun @bun-cjs header, WV8StW string-array shuffle, numeric/char table n7gIxM, custom charset decoder hc1jfK9) with no readable identifiers or URLs, and is not referenced anywhere from index.js — it exists only to be run by the downloaded Bun runtime at preinstall. setup.mjs itself is javascript-obfuscator-style renamed (_0x* identifiers, string-key indirection objects). The alternate-runtime choice hides the executed payload from Node-based static analysis, and the file name math_init has no relationship to any advertised AI-SDK feature. This is the alternate-runtime-dropper pattern: install-time execution of opaque bytes under a runtime fetched at install, on a package whose stated purpose does not require Bun.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
3.32.2

Indicators of compromise (SHA-256)

b9f4dd8e0c507b2c232a260121c846acbeaf98a941b08896ba5db052030d73f7
c5754da90cb12c17fa79ceddb48595f401967ac56008f3176b2ae9fb9ab83758

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @picsart/ai-sdk (version 3.32.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @picsart/ai-sdk across your stack and pipelines.

  2. If you installed it — respond

    @picsart/ai-sdk is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @picsart/ai-sdk was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks @picsart/ai-sdk before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @picsart/ai-sdk on npm has been identified as a malicious package (version 3.32.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-cxqq-phxq-9v9rIN-MAL-2026-014206

References

Credits

  • Aikido Security · finder
  • Amazon Inspector · finder
  • SafeDep · finder
  • Socket Threat Research Team · finder

Detect & block this

O3 blocks @picsart/ai-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@picsart/ai-sdk (npm) malicious package — MAL-2026-11781 | O3 Security