NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

ai-pro-sdknpm

Advisory published Updated

ai-pro-sdk is a confirmed malicious npm package (MAL-2026-10629) that executes malicious code on install (malicious versions 2.0.1, 2.0.2, 2.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ai-pro-sdk (npm)

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

What this malware does

[email protected] is advertised as a Vercel AI SDK provider for Claude via the Claude Agent SDK, but the published tarball ships no code: package.json declares main as./dist/index.js and files as dist/**/*, yet no dist/ directory is present, and the prepare script is a console.log no-op ('Build skipped...'). Alongside the expected @ai-sdk/provider and @anthropic-ai/claude-agent-sdk entries, package.json declares a runtime dependency on data-blockv@^1.0.1, a package unrelated to the advertised purpose and not referenced anywhere in the tarball or README. The net effect of npm install ai-pro-sdk is resolution and installation of data-blockv into the installer's node_modules; because the host package has no functional code, its only on-install effect is to pull this unrelated transitive dependency. This matches the dropper-shell shape where the lure package's advertised functionality is a cover and the actual code-execution surface lives in a sibling dependency name that has no legitimate reason to be present.

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

4 flagged
2.0.12.0.22.0.32.0.4

Indicators of compromise (SHA-256)

14b76dc0668149523b0c451c3ceb71dfceb5dcadc8634182287917c646b54067
b035f137addcf0118c3d042ece322d0fdde054e4ed283317d3b2adb309e38689
e343ae51cdc038956270ff7c3ee3d4bc6da3868178be91675567399a5f07a402
451b890a986e88fce01d29473c9e9819a70d0c0429587998beb255f153c6dd5f
62aff6cca33a993a174b9c33408e7e7dac2006967a532a1d15037678aa91cfe2

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for ai-pro-sdk (4 malicious versions).

  2. If you installed it — respond

    Remove ai-pro-sdk from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If ai-pro-sdk was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. ai-pro-sdk on npm has been identified as a malicious package (versions 2.0.1, 2.0.2, 2.0.3, 2.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010596IN-MAL-2026-010597IN-MAL-2026-010739GHSA-pw5v-v543-v4mpIN-MAL-2026-013058

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks ai-pro-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

ai-pro-sdk (npm) malicious package — MAL-2026-10629 | O3 Security