Which versions of aikaf668897 are malicious?

The following npm versions of aikaf668897 are flagged malicious: 1.0.3. Treat any of these as compromised.

How do I remediate aikaf668897 if I installed it?

aikaf668897 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

If aikaf668897 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 aikaf668897 part of a known attack campaign?

Yes — aikaf668897 is associated with the IN-MAL-2026-007084 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 aikaf668897 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 aikaf668897 (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aikaf668897 across your stack and pipelines.

Malicious package

aikaf668897npm

aikaf668897 is a confirmed malicious npm package (MAL-2026-6216) that opens a backdoor for remote access (malicious version 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aikaf668897 (npm)

MAL-2026-6216

Immediate action

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

npm uninstall aikaf668897

What this malware does

On npm install, the package's postinstall hook (node scripts/postinstall.js) spawns a detached background Node process running scripts/shell.js with detached: true, stdio: 'ignore', windowsHide: true and .unref(), so the child survives npm install completion and runs invisibly. scripts/shell.js opens a TCP socket to the hardcoded bare IP 114.67.90.67 on port 3333 and pipes a local shell (/bin/sh on Unix, powershell.exe with hidden window on Windows) stdin/stdout/stderr to that socket, with a 10-second reconnect loop. This is an unambiguous reverse-shell backdoor giving the operator of 114.67.90.67 interactive command execution on the installer's machine. The package's advertised purpose (a string-manipulation utility, with index.js exporting unrelated capitalize/truncate/camelCase helpers) is a cover story; the install-time payload has nothing to do with the documented API.

Malicious versions

1 flagged

1.0.3

Indicators of compromise (SHA-256)

450730a92143c06530923dacda588a17252ebc7edc9ddf71ff520446de5a3293

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for aikaf668897 (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aikaf668897 across your stack and pipelines.
If you installed it — respond
aikaf668897 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If aikaf668897 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 aikaf668897 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. aikaf668897 on npm has been identified as a malicious package (version 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007084

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database