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

character-ai-sdknpm

Advisory published Updated

character-ai-sdk is a confirmed malicious npm package (MAL-2026-20196) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in character-ai-sdk (npm)

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

What this malware does

[email protected] presents itself as a persona/memory SDK but its main entry (index.mjs → personas.mjs) top-level imports./cache-warm.mjs, a ~300 KB obfuscator.io-style blob (hex-renamed string array of base64+XOR entries) with no library-shaped exports. Decoded property-access artifacts in the blob reference process.exit, process.pid, hostname, and child-process APIs, consistent with runtime-resolved process control and host enumeration executed on require/import. Three additional obfuscated siblings of the same shape (build-cache.mjs ~200 KB, cache-sweep.mjs ~290 KB, workspaces.js ~280 KB) are staged next to the main-reachable loader. The tarball also ships platform-specific native addons at native/{linux,darwin,win32}/{x64,arm64}/cache-probe.node whose exported symbols are a vendored VM-detection library (VMDetect, VM::qemu_fw_cfg, VM::vbox_module, VM::hypervisor_bit, VM::smbios_vm_bit, VM::dmidecode, VM::chassis_vendor, VM::mac_address_check), confirmed by native/LICENSE-node-vm-detect.txt. A persona-lookup SDK has no legitimate need for hypervisor/QEMU/VirtualBox/DMI/MAC-based sandbox detection, and the combination — heavy obfuscated loader reachable from the main entry, multiple identical-shape dropper siblings staged alongside it, and cross-platform anti-sandbox native addons — matches the shape of a staged, sandbox-evading dropper that executes on module load.

Malicious versions

2 flagged
1.0.01.0.1

Indicators of compromise (SHA-256)

2cfbfb7f36ef7b7955f6df670119892a13e2fcca6526dc75b68dcda4a46ca3d5
e6af43ad88e14f748ddb331c356e9eca8285d02e9982c15a3ebc2e5c075183d8

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for character-ai-sdk (2 malicious versions).

  2. If you installed it — respond

    Remove character-ai-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 character-ai-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. character-ai-sdk on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022875IN-MAL-2026-022876

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks character-ai-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

character-ai-sdk (npm) malicious package — MAL-2026-20196 | O3 Security