This Week in Cybersecurity: PyPI Package Poisoned, a Persistent Cisco Backdoor, and Developer Tools Compromised
By Heather Walters
A week dominated by supply chain risk and leadership gaps at the nation's top cyber agency.
It was a busy week for supply chain security. From the million-plus downloads that were compromised on PyPl, to the CISA reveal that a state-sponsored backdoor called FIRESTARTER had persisted on a federal Cisco firewall through months of patching, there's a lot to cover.
A coordinated attack on Checkmarx cascaded into a brief compromise of the Bitwarden CLI on npm. Researchers published new findings on a Lua-based malware framework predating Stuxnet by five years. And CISA's long-stalled director nominee formally withdrew after 13 months in Senate limbo. Here's what you need to know.
Explore this content with AI:
ChatGPT | Perplexity | Claude | Google AI Mode
ML monitoring tool with 1 Million monthly downloads compromised on PyPI
On Friday April 25, unknown attackers exploited a vulnerability in the GitHub Actions workflow of element-data — a popular open source CLI used to monitor performance and anomalies in machine-learning systems — to gain access to its signing keys and publish a malicious version. The tampered package (version 0.23.3) was pushed simultaneously to the Python Package Index and the project's Docker image account. When run, it scoured systems for sensitive data, including dbt profiles, warehouse credentials, cloud provider keys, API tokens, SSH keys, and the contents of any .env files. CI/CD runners were particularly exposed given the broad set of secrets typically mounted at runtime. The malicious version was removed roughly 12 hours later, on Saturday. Elementary Cloud, the Elementary dbt package, and all other CLI versions were not affected.
Developers are urging anyone who installed version 0.23.3 to pin explicitly to elementary-data==0.23.4, delete cache files, check for the malware's marker file on any machine where the CLI ran, and rotate all credentials that were accessible from the affected environment.
Why it matters: User-developed GitHub Actions workflows are a well-documented weak point in open source security — and this incident is a reminder that even widely-used, legitimate tools can become credential-harvesting payloads overnight. With 1 million monthly downloads, the exposure window of 12 hours is significant. If element-data ran in your pipeline this weekend, treat it as a credential exposure.
FIRESTARTER: APT backdoor survived months of patching on a federal Cisco firewall
On April 23, CISA and the UK's NCSC published a joint malware analysis report on FIRESTARTER, a custom Linux backdoor found on a U.S. federal civilian agency's Cisco Firepower device running ASA software. The malware is attributed to UAT-4356 (also tracked as Storm-1849), the same threat actor behind the 2024 ArcaneDoor espionage campaign. CISA and Cisco stopped short of formal nation-state attribution, though earlier Censys analysis pointed toward China.
FIRESTARTER hooks into LINA, Cisco ASA's core network processing engine, and intercepts WebVPN authentication requests containing a hidden trigger. The implant survives firmware updates and graceful reboots by writing itself back into the device boot sequence. The only confirmed remediation is a hard power cycle followed by full device reimaging. CISA confirmed the agency was first compromised in September 2025, and that attackers used the backdoor to redeploy a second-stage payload called LINE VIPER as recently as March 2026. An updated Emergency Directive (ED 25-03) requires federal civilian agencies to audit affected Cisco hardware and submit memory snapshots to CISA by April 30.
Why it matters: Patching alone is not enough if a device was compromised before the patch was applied. Organizations running internet-facing Cisco ASA or FTD devices should verify whether reimaging is necessary — not just whether patches are current.
Checkmarx and Bitwarden developer tools hit in linked supply chain attack
On April 22, attackers linked to a group tracked as TeamPCP compromised Checkmarx's KICS Docker images, GitHub Actions, and two VS Code extensions, pushing malicious versions to official distribution channels. The malware harvested credentials from CI/CD environments and exfiltrated them to an attacker-controlled domain impersonating Checkmarx.
The attack then reached Bitwarden. Because Bitwarden's CI/CD pipeline uses the Checkmarx KICS GitHub Action to run security scans, the compromised Action harvested Bitwarden's GitHub and Azure credentials, which were used to push a malicious version of the Bitwarden CLI (@bitwarden/cli@2026.4.0) to npm. The package was live for roughly 90 minutes before being pulled. Bitwarden confirmed no vault data or production systems were affected, but any developer who installed the package during that window should rotate GitHub tokens, cloud keys, SSH keys, and CI/CD secrets.
Why it matters: Compromising a widely-used scanning tool gives attackers a foothold in the pipelines of every project that uses it. The exposure window was short, but in a high-volume ecosystem like npm, 90 minutes is enough for meaningful downstream impact.
fast16: Newly analyzed malware predates stuxnet by five years
Researchers at SentinelOne published a detailed analysis this week of fast16, a previously undocumented Lua-based malware framework dating to approximately 2005 — at least five years before Stuxnet. The framework targeted high-precision calculation software in industrial facilities, tampering with computational results rather than destroying hardware directly.
The discovery traces back to a text file in the "Lost in Translation" leak published by the Shadow Brokers in 2016–2017, which contained tools allegedly stolen from the NSA-linked Equation Group. Researchers Vitaly Kamluk and Juan Andrés Guerrero-Saade linked a string inside a binary called svcmgmt.exe to the broader fast16 framework. Stuxnet has long been considered the first known digital weapon designed for industrial sabotage. fast16 suggests that state-sponsored offensive cyber programs were more advanced, and operating earlier, than the public record has reflected.
Why it matters: The history of state-sponsored cyberweapons is still being written — and what's been disclosed may represent only a fraction of what was developed. For threat intelligence teams, fast16 is a useful reminder that historical leaks still contain unanswered questions.
CISA director nominee withdraws after 13 months without a U.S. senate vote
Sean Plankey, President Trump's twice-nominated pick to lead CISA, formally withdrew his nomination on April 22 after 13 months without a Senate confirmation vote. In a letter to the White House, Plankey wrote that it had "become clear the Senate will not confirm me" and cited the toll on his family.
The delay was not driven by concerns about Plankey's qualifications — he had broad support in the cybersecurity community and cleared a Senate committee vote last July. The holdups came from two Republican senators with unrelated grievances: Sen. Rick Scott (R-FL) over a Coast Guard shipbuilding contract, and Sen. Ted Budd (R-NC) over disaster recovery funding. CISA now falls to acting director Nick Anderson, as the agency continues to operate with roughly a third fewer staff than it had in early 2025 and faces a proposed $700 million budget cut.
Why it matters: CISA has been without confirmed permanent leadership for an extended period, during a stretch of sustained nation-state cyber activity. The FIRESTARTER disclosure this same week is a concrete example of what that operating environment looks like.
Final thoughts
The common thread this week is the gap between assumed and actual security posture. Vercel assumed OAuth grants were low-risk. Federal agencies assumed patching their firewalls was sufficient. Developers assumed tools in their CI/CD pipeline were trustworthy. In each case, attackers found the space between assumption and reality.
The practical takeaways: audit third-party OAuth grants, treat Cisco ASA and FTD patching as potentially insufficient without reimaging, rotate credentials if your environment pulled the affected Bitwarden CLI package, and check back next Tuesday for another roundup.
Ready to see how OpenVPN can help protect your organization from attacks?
Try the self-hosted Access Server solution or managed CloudConnexa service for free — no credit card required.
See Which One is Right for YouHeather is a writer for OpenVPN.