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

@picsart/gen-ainpm

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

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

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

What this malware does

npm/@picsart/gen-ai 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's scripts.preinstall runs setup.mjs, which downloads the Bun runtime from GitHub when not already present and then invokes Bun to execute the sibling file math_init.js at install time. math_init.js is a 727 KB single-line, heavily obfuscated blob using a rotating string-array (WV8StW) and a custom-alphabet decoder (hc1jfK9) over an opaque literal, with hex-named identifiers throughout; no plaintext endpoints, purpose strings, or references relating to the package's advertised generative-AI CLI are visible. Delivery through an alternate runtime (Bun) executed on npm install routes the payload around Node-based install-time inspection, and the depth of obfuscation is consistent with hiding network destinations and behavior. The @picsart scope is a known target of recent npm supply-chain compromises; the combination of alt-runtime delivery, opaque payload, and misleading filename (math_init.js) inside a gen-ai package is not consistent with legitimate install-time work.

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
2.55.11

Indicators of compromise (SHA-256)

6038bf4f1c4bdd5d2a48c654042f45f2802763031af9f8a40b171ce6044360d4
5ab726225abddf108e6f49d02b0c6ff1b250a268b07ab5df0f05ed8079b71883

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/gen-ai (version 2.55.11). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @picsart/gen-ai across your stack and pipelines.

  2. If you installed it — respond

    @picsart/gen-ai 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/gen-ai 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/gen-ai 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/gen-ai on npm has been identified as a malicious package (version 2.55.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4p68-ppf4-vjwcIN-MAL-2026-014207

References

Credits

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

Detect & block this

O3 blocks @picsart/gen-ai-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/gen-ai (npm) malicious package — MAL-2026-11782 | O3 Security