Executive Summary
In July 2026, cybersecurity researchers identified a campaign distributing a Python-based remote access trojan (RAT) named ChocoPoC through trojanized proof-of-concept (PoC) exploits on GitHub. Unlike previous incidents where malware was embedded directly in exploit files, this campaign introduced malicious Python packages into the PoC's dependency list. When victims cloned these repositories, a trojanized package named 'frint' was automatically installed, which subsequently fetched another malicious package, 'skytext.' This package contained a compiled Python extension that decrypted and executed additional code, ultimately downloading the ChocoPoC RAT from a Mapbox dataset. The RAT possessed capabilities such as executing arbitrary commands, uploading files, and collecting sensitive data, including browser credentials and network configurations. (bleepingcomputer.com)
This incident underscores a growing trend where threat actors exploit trusted platforms like GitHub to distribute malware, targeting professionals who frequently utilize PoC exploits for research and testing. The sophisticated method of embedding malicious code within dependency packages highlights the need for heightened vigilance when sourcing code from public repositories. As attackers continue to refine their techniques, the cybersecurity community must adapt by implementing stricter code verification processes and promoting awareness about the risks associated with unverified code. (bleepingcomputer.com)
Why This Matters Now
The ChocoPoC campaign highlights the increasing sophistication of supply chain attacks targeting cybersecurity researchers through trusted platforms like GitHub. As threat actors refine their methods, it's imperative for professionals to exercise caution when sourcing code and to implement robust verification processes to mitigate potential risks. (bleepingcomputer.com)
Attack Path Analysis
Attackers compromised cybersecurity researchers by embedding malicious Python packages into proof-of-concept (PoC) exploits on GitHub. Upon execution, the malware escalated privileges to gain broader system access, moved laterally within the network, established command and control channels, exfiltrated sensitive data, and potentially disrupted operations.
Kill Chain Progression
Initial Compromise
Description
Attackers embedded malicious Python packages into PoC exploits on GitHub, which researchers downloaded and executed, leading to system compromise.
Related CVEs
CVE-2025-14847
CVSS 7.5A vulnerability in MongoDB Server allows pre-authentication memory disclosure via OP_COMPRESSED messages, potentially exposing sensitive data.
Affected Products:
MongoDB Inc. MongoDB Server – 3.6.0 to 4.4.29, 5.0.0 to 5.0.31, 6.0.0 to 6.0.26, 7.0.0 to 7.0.27, 8.0.0 to 8.0.16, 8.2.0 to 8.2.2
Exploit Status:
proof of conceptCVE-2026-10520
CVSS 10An OS command injection vulnerability in Ivanti Sentry allows remote attackers to execute arbitrary commands on the underlying operating system.
Affected Products:
Ivanti Sentry – All versions prior to 9.17.0
Exploit Status:
exploited in the wild
MITRE ATT&CK® Techniques
Supply Chain Compromise: Compromise Software Dependencies and Development Tools
Command and Scripting Interpreter: Python
User Execution: Malicious Link
Application Layer Protocol: Web Protocols
Screen Capture
Data from Local System
File and Directory Discovery
Exfiltration Over C2 Channel
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Ensure all system components and software are protected from known vulnerabilities
Control ID: 6.2
NYDFS 23 NYCRR 500 – Cybersecurity Policy
Control ID: 500.03
DORA – ICT Risk Management Framework
Control ID: Article 6
CISA ZTMM 2.0 – Data Security
Control ID: Pillar 3: Data
NIS2 Directive – Cybersecurity Risk Management Measures
Control ID: Article 21
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Computer/Network Security
Cybersecurity researchers directly targeted through trojanized PoC exploits delivering ChocoPoC RAT, compromising security professionals who test vulnerability code regularly.
Computer Software/Engineering
Software developers vulnerable to supply chain attacks via malicious PyPI packages embedded in GitHub repositories, enabling credential theft and system compromise.
Information Technology/IT
IT professionals testing security tools face elevated risk from weaponized exploits targeting multiple enterprise platforms including FortiWeb, PAN-OS, and Ivanti systems.
Higher Education/Acadamia
Academic security researchers and students analyzing vulnerability research exposed to sophisticated malware delivery through legitimate-appearing proof-of-concept exploit repositories.
Sources
- New ChocoPoC malware targets researchers via trojanized PoC exploitshttps://www.bleepingcomputer.com/news/security/new-chocopoc-malware-targets-researchers-via-trojanized-poc-exploits/Verified
- CVE-2025-14847 Detailhttps://nvd.nist.gov/vuln/detail/CVE-2025-14847Verified
- CVE-2026-10520 Detailhttps://nvd.nist.gov/vuln/detail/CVE-2026-10520Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Aviatrix Zero Trust CNSF is pertinent to this incident as it can significantly limit the attacker's ability to move laterally, escalate privileges, and exfiltrate data by enforcing strict segmentation and identity-aware policies.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: The CNSF would likely limit the initial compromise's impact by enforcing strict workload isolation, reducing the attacker's ability to access other systems.
Control: Zero Trust Segmentation
Mitigation: Zero Trust Segmentation would likely limit the attacker's ability to escalate privileges by enforcing strict access controls based on identity and context.
Control: East-West Traffic Security
Mitigation: East-West Traffic Security would likely limit lateral movement by enforcing strict controls on internal traffic, reducing the attacker's ability to spread across the network.
Control: Multicloud Visibility & Control
Mitigation: Multicloud Visibility & Control would likely limit command and control activities by providing comprehensive monitoring and control over network traffic, reducing the attacker's ability to communicate with external servers.
Control: Egress Security & Policy Enforcement
Mitigation: Egress Security & Policy Enforcement would likely limit data exfiltration by enforcing strict policies on outbound traffic, reducing the attacker's ability to transmit sensitive data externally.
The CNSF's comprehensive controls would likely limit the overall impact by containing the attacker's activities and reducing the blast radius of the incident.
Impact at a Glance
Affected Business Functions
- Vulnerability Research
- Penetration Testing
- Security Analysis
Estimated downtime: 3 days
Estimated loss: $50,000
Potential exposure of sensitive research data, including exploit code and proprietary analysis.
Recommended Actions
Key Takeaways & Next Steps
- • Implement Zero Trust Segmentation to restrict lateral movement and limit the spread of malware within the network.
- • Enforce Egress Security & Policy Enforcement to monitor and control outbound traffic, preventing unauthorized data exfiltration.
- • Utilize Threat Detection & Anomaly Response systems to identify and respond to malicious activities promptly.
- • Apply Inline IPS (Suricata) to detect and block known exploit patterns and malicious payloads during traffic inspection.
- • Ensure Multicloud Visibility & Control to maintain comprehensive oversight and centralized policy management across cloud environments.



