bytekit
Affected
- Versions:
3.4.1,3.4.2
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in bytekit (PyPI)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (0bbaea22b635a4a8425964572b733b806f45714a9090492d1c39d545088fe336)
The package was found to contain malicious code or consuming dependency that contains malicious code
Source: kam193 (f4594bf7abce5a96c971ecc42fc52eec534a545cfc614c1b8f3b8d18ca02dd9d)
The campaign consists of multiple packages. The trigger sits in the package 'procwire,' which depends on two others. During installation, procwire uses schemavault and bytekit packages. The first one holds the URL holding malware (in two places, once as steganography in the bundled image and once as a fallback just as a list of encoded bytes). The bytekit implements simple custom decoding used to retrieve back the URL in the fallback method. Additionally, procwire is also a dependency of confighub, turning another package into malware. The downloaded executable is run and quickly removed. The executable likely contains an infostealer and contacts the domain 030502[.]xyz
---
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-07-procwire
Reasons (based on the campaign):
Not rated by the source.
3.4.1, 3.4.2None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0