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

nikou-nodenpm

Advisory published Updated

nikou-node is a confirmed malicious npm package (MAL-2026-4620) that steals credentials and exfiltrates sensitive data (malicious version 2.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nikou-node (npm)

MAL-2026-4620
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall nikou-node

What this malware does

utils/BotClient.js hardcodes a Feishu/Lark appId (cli_a88b12e0b9b51013) and appSecret (aBRv7CbiWuL7csrMavfLvc5sMW5B4Ky7) as default constructor values, instantiating a lark.Client capable of sending messages, fetching users, and adding members to chats within the author's Lark tenant. Anyone who installs the package receives these credentials in plain source and can impersonate the author's Feishu bot against the Lark API, with Lark/the author's tenant as the third-party victim. Additional concerns observed but not the basis for this verdict: utils/UsageStatClient.js hardcodes credentials for a MySQL telemetry host (mysql-hk-global-feature.hszq8.com) and sends per-CLI-invocation hostname/identity data to it; commands/nb-init.js embeds a plaintext GitLab PAT for the author's own internal GitLab over HTTP. Those are author self-harm / undisclosed telemetry rather than installer harm.

Malicious versions

1 flagged
2.0.1

Indicators of compromise (SHA-256)

d4634b70c99dd84c499d573350a00e86b09e8caaf34786d60b118ce12c64b426

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for nikou-node (version 2.0.1).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-003807

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks nikou-node-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

nikou-node (npm) malicious package — MAL-2026-4620 | O3 Security