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

nextjs-chat-with-ai-servicenpm

Malicious code in nextjs-chat-with-ai-service (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3241
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall nextjs-chat-with-ai-service

What this malware does

The package nextjs-chat-with-ai-service was found to contain malicious code.

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.

The OpenSSF Package Analysis project identified 'nextjs-chat-with-ai-service' @ 99.9.9 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged
99.9.9

Indicators of compromise (SHA-256)

65cc0b46517cf92afa63e78b4bab53d01aa4592f31b5d94225bba97bd3d7441a
8ff3e52e4957291f626e1225ab3b81194c80cd8c6037f943298f6170f98dbe9b
f8d48f7c46da7693f8c544c03bb5f1d94e0162374ca0ca81a8175695c4420f8c

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove nextjs-chat-with-ai-service 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 nextjs-chat-with-ai-service 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 nextjs-chat-with-ai-service 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. nextjs-chat-with-ai-service on npm has been identified as a malicious package (version 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-88fc-46q8-6h4p

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks nextjs-chat-with-ai-service-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.

nextjs-chat-with-ai-service (npm) malicious package — MAL-2026-3241 | O3 Security