Which versions of aikaf6688812 are malicious?

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

How do I remediate aikaf6688812 if I installed it?

Remove aikaf6688812 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.

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

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

Is aikaf6688812 part of a known attack campaign?

Yes — aikaf6688812 is associated with the IN-MAL-2026-007083 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 aikaf6688812 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for aikaf6688812 (version 1.0.3).

Malicious package

aikaf6688812npm

Advisory published Jun 19, 2026Updated Jun 19, 2026

aikaf6688812 is a confirmed malicious npm package (MAL-2026-6215) that executes malicious code on install (malicious version 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aikaf6688812 (npm)

MAL-2026-6215

Immediate action

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

npm uninstall aikaf6688812

What this malware does

package.json declares a postinstall hook that runs scripts/postinstall.js, which spawns scripts/shell.js as a detached, stdio-ignored background process (spawn(process.execPath, [path.join(__dirname, 'shell.js')], { detached: true, stdio: 'ignore', windowsHide: true })). scripts/shell.js opens a TCP socket to the hardcoded host 114.67.90.67 on port 3334 and pipes the local shell to that socket — /bin/sh -i on POSIX, hidden powershell.exe on Windows — with an automatic reconnect loop every 10 seconds. Any machine that runs npm install aikaf6688812 immediately yields persistent interactive shell access at the operating-system level to whoever controls 114.67.90.67. The package's stated purpose is string utilities; the network and shell behavior is unrelated to that purpose. Author metadata (frontend-dev) and the repo URL point to a non-existent GitHub project, consistent with a disposable lure.

Malicious versions

1 flagged

1.0.3

Indicators of compromise (SHA-256)

fcdebe342ec1c629835301869934fab1a4800c98116a337ec33b05def92d33e7

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for aikaf6688812 (version 1.0.3).
If you installed it — respond
Remove aikaf6688812 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.
Did it already run?
If aikaf6688812 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. aikaf6688812 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-007083

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks aikaf6688812-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database