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

aichannelPyPI

aichannel is a confirmed malicious PyPI package (MAL-2026-11415) that steals credentials and exfiltrates sensitive data (malicious version 0.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aichannel (PyPI)

MAL-2026-11415
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall aichannel

What this malware does

Package connects to a hardcoded C2 socket server (SOCKET_SERVER_HOST/SOCKET_SERVER_PORT from cognikit.config) and runs a typed-message session loop that gives the remote peer full control of the installer's host. handlers.handle_command base64-decodes attacker-supplied strings and passes them to subprocess.run(..., shell=True) via command.execute_command, yielding arbitrary shell RCE. The session dispatch also implements download (write attacker files to disk), upload/archive (exfiltrate arbitrary files or zipped directories to the C2), install/grabext (install or steal browser extensions), and keylog (upload keylogger output). launcher.run_helper spawns a background daemon that keystrokes and monitors the clipboard, swapping crypto wallet addresses with attacker-supplied replacements fetched from {DJANGO_API_URL}/address and decoded via base64 + XOR with the static key 'w3x'; the keylog file is later uploaded via upload_file_to_public_api(kl.log_path, machine_id, 'key'). The obfuscated wallet-replacement list and the clipper/keylogger integration confirm hostile intent.

In this campaign, some packages (e.g. cognikit, aiassistcore) are pulled as dependencies and contain the C2 configuration and the malicious functionality, while others (like aichannel) provide fake functionality and silently execute malicious actions from dependencies. The malicious functionality is oriented to replace the copied cryptocurrency wallet addresses with these controlled by the attacker and downloaded from the C2 server, exfiltrating browser data, establishing a remote control over the device, placing malicious extensions in browsers.

IoCs are consistent with those previously attributed to North Korea's "Contagious Interview" campaign. The known TTP suggest these packages are used as dependencies in malicious interview assessments or cryptocurrency projects.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-07-cognikit

Reasons (based on the campaign):

  • crypto-related

  • The malicious code is intentionally included in a dependency of the package

  • keylogger

  • clipboard-modify

  • exfiltration-browser-data

  • persistence

  • rat

  • The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.

Malicious versions

1 flagged
0.1.2

Indicators of compromise (SHA-256)

21e18e6e4016bf07f11edb272a08fb26268b2fbfe0b42a4ba502df368ce05b01
7e51fdc38d5678b9b9a96014b69db1062b6ecc71b8986a837b4e9ba8d03d7214

Detection & response playbook

Credential / info stealer
  1. Find it

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

  2. If you installed it — respond

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

Campaign

2026-07-cognikitIN-MAL-2026-010989

References

Credits

  • Amazon Inspector · finder
  • Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks aichannel-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

aichannel (PyPI) malicious package — MAL-2026-11415 | O3 Security