Which versions of kijai are malicious?

The following npm versions of kijai are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate kijai if I installed it?

kijai 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.

I already installed kijai — how do I know if it already compromised me?

If kijai 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.

Is kijai part of a known attack campaign?

Yes — kijai is associated with the GHSA-5mgj-24pj-pj6f, IN-MAL-2026-012918 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find kijai across my projects, lockfiles, and CI pipelines?

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

Malicious package

kijainpm

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

Malicious code in kijai (npm)

MAL-2026-11014

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall kijai

What this malware does

The package advertises itself as a high-throughput bulk-mail tool and ships every one of its ~50 JS files (cli.js, denv.js, helpers.js, all commands/.js, all functions/**/.js, queue/, web/, utils/*) as obfuscator.io-packed bundles with rotated string arrays, hex-named identifiers, and self-defending wrappers. README is a single sentence with no API docs. Functionality includes SOCKS proxy rotation (with four hardcoded proxies in _init/socks.txt), multi-threaded SMTP sending, fake-identity generation, masked-email helpers, an encryptAndObfuscateAttachment3 helper that injects eval(decode(...)) zero-width-character payloads into HTML attachments, EML smuggling, and Microsoft account-existence probing via GetCredentialType. The verify subcommand fetches https://login.live.com/login.srf and runs eval() on a regex-extracted var ServerData = {...} block from the response body, which is unsafe content evaluation but fires only when an operator explicitly runs kijai verify. package.json declares no preinstall/install/postinstall/prepare scripts; main and bin both point at a commander-based cli.js, so npm install kijai and a transitive require() do not auto-execute the abusive code paths. The advertised functionality targets third-party mail recipients and Microsoft account endpoints, not the developer who installs the package, so this does not satisfy the installer-harm gate (no exfiltration, no credential theft, no install-time destruction, no backdoor against the installer). Wholesale obfuscation of an abusive-purpose tool published openly on npm is policy-relevant and warrants human review for registry-abuse / ToS grounds, but it is not a supply-chain attack against installers under this system's scope.

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

0.0.2

Indicators of compromise (SHA-256)

f5db4f6fb4cd8bc8073e03771776ba865f51f852120bd44162573774905ccf22

86481ee3f08109eeaec60a41afb7c2e8d03efd680cc5bf846bdc342ec4205205

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for kijai (version 0.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kijai across your stack and pipelines.
If you installed it — respond
kijai 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.
Did it already run?
If kijai 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.
How O3 protects you
O3 blocks kijai 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. kijai on npm has been identified as a malicious package (version 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-5mgj-24pj-pj6fIN-MAL-2026-012918

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks kijai-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database