Skip to content

Malicious code in cognikit (PyPI)

Malware Published Jul 31, 2026 to the GitHub Advisory Database • Updated Jul 31, 2026

Package

pip cognikit (pip)

Affected versions

= 0.1.2

Patched versions

None

Description

Source: kam193 (e0cdc137d19f19df47efa6fae6d52ec6eda48eb2f1915ac4eb77787956d10aba)

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.


Credit: OpenSSF (source)

References

Published to the GitHub Advisory Database Jul 31, 2026
Reviewed Jul 31, 2026
Last updated Jul 31, 2026

EPSS score

Weaknesses

Embedded Malicious Code

The product contains code that appears to be malicious in nature. Learn more on MITRE.

GHSA ID

GHSA-h78x-87rw-9vm8

Source code

No known source code
Improvements are not currently accepted on this advisory because this package is malware and has no patched versions. If there is something to change, please open an issue at https://github.com/github/advisory-database/issues.