iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Hackaday’s April 25, 2025 security roundup covered two especially useful lessons: a malicious release of the XRP Ledger JavaScript SDK could expose wallet secrets when key-handling code ran, and a malicious MCP tool description could influence an AI model before the tool was called. The issue also summarized reports about Zyxel firewalls, STM32 fault injection, SK Telecom, Commvault, Chrome, and cryptography. These are historical reports, not a statement of current patch or incident status.
What happened with the XRP Ledger JavaScript package?
Aikido reported that its monitoring system flagged five new releases of the npm package xrpl at 20:53 GMT on April 21, 2025. Those versions did not match the then-current GitHub releases. Aikido’s code review found a malicious checkValidityOfSeed() function that sent its argument in an HTTP ad-referral header to 0x9c[.]xyz. The function was called on wallet creation or derivation paths with seed or private-key values, making this credential-theft code in an official SDK package—not merely an unusual release.
The affected-version window Aikido reported ran from April 21 at 20:53 GMT+0 to April 22 at 13:00 GMT+0. Its analysis listed these versions:
Recommended Free Tools
| Package version | Status in Aikido’s April 2025 report |
|---|---|
4.2.1 |
Compromised release |
4.2.2 |
Compromised release |
4.2.3 |
Compromised release |
4.2.4 |
Compromised release |
2.14.2 |
Compromised release |
4.2.5 |
Remediation release identified by Aikido at the time |
2.14.3 |
Remediation release identified by Aikido at the time |
These are historical incident indicators, not a guarantee that the listed remediation releases remain the project’s current recommendation. Check the current npm package and project advisories before changing dependencies or treating an installation as safe.
#1 Best Overall
What an affected dependency means for a wallet
Installation of an affected package does not, by itself, establish that a wallet secret was processed. The key question is whether wallet creation, derivation, or another relevant code path ran with a seed or private key. Aikido’s contemporaneous guidance was to assume any seed or private key processed by the malicious code was compromised, stop using the associated keys, and move assets to a new wallet created with a new key. Anyone assessing a past exposure should examine the lockfile and package version, then determine whether key-handling code ran; if a secret was processed, follow current project and wallet-provider guidance for replacing it.
Aikido said the package had more than 140,000 weekly downloads in its April 22, 2025 report. Hackaday reported 452 downloads of the malicious releases during the few hours they were available. These are package-download figures, not counts of affected people, compromised wallets, or stolen funds.
How did MCP “line jumping” work?
Trail of Bits described an MCP client that calls tools/list when it connects to a server and places the returned tool descriptions in the model’s context. A malicious server can hide instructions in a description; those instructions may influence the model before a user explicitly invokes that tool. Trail of Bits calls this “line jumping”; the pattern is also known as tool poisoning.
The distinction matters: approving or blocking a tool call controls whether the tool executes, but it may not prevent a description from influencing the model after the client has already ingested it. Trail of Bits put the risk this way: “MCP servers can manipulate model behavior without ever being invoked.”
The report outlined possible paths including code exfiltration, insecure code suggestions, and manipulation of security alerts. These were attack scenarios, not confirmed outcomes of that particular report. Trail of Bits recommended reviewing and vetting MCP servers and their descriptions, watching for new or changed tools, disabling servers that are not needed, avoiding automatic approval of sensitive commands, and reviewing proposed actions.
What did the other reports in the roundup cover?
Zyxel USG FLEX H-series
Hackaday summarized a reported chain affecting Zyxel USG FLEX H-series firewall and router devices: an authenticated VPN user could use SSH forwarding and a local PostgreSQL service, then take advantage of Recovery Manager behavior to obtain root access. The technical account was attributed to hn Security; Hackaday’s summary was the basis for this description, so the chain should not be treated here as independently corroborated. The roundup does not establish that every device was exploited or give a current patch-status assessment.
STM32F401CC voltage fault injection
Anvil Secure’s April 18, 2025 demonstration used voltage fault injection to bypass Read Out Protection (RDP) on an STM32F401CC. Its setup included an STM32F401CC development board, a ChipWhisperer-Lite, a USB-UART TTL converter, and an ST-Link programmer. The write-up describes the need for a precise timing window and explicitly limits its observations to the STM32F401CC. It is a physical-access research demonstration, not evidence that STM32 devices generally share the same weakness. ChipWhisperer-Lite was equipment used in the demonstration, not a fix for the issue.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteSK Telecom
Hackaday reported that SK Telecom had been breached and was offering customers free SIM-swap protection. The roundup said public information was limited at the time; it cited SecurityWeek’s contemporary report. The protection offer alone does not establish what data was accessed or the full scope of the incident.
Best Value
Commvault, Chrome, and cryptography
- Commvault: Hackaday’s “Bits and Bytes” section relayed WatchTowr’s report of a pre-authentication remote-code-execution issue involving malicious archive handling. That is vulnerability reporting; the roundup does not establish exploitation in the wild.
- Chrome: The roundup cited SSD Disclosure’s report of two use-after-free bugs mitigated with MiraclePtr. It did not establish further details about exploitation or current browser status.
- ChaCha20 and AES: Phase argued that ChaCha20’s simplicity can be an advantage relative to AES. This is commentary, not a standards decision or a finding that one cipher is universally preferable.
How should readers use this roundup now?
The reports describe events and claims published in April 2025; they do not establish current package releases, product fixes, incident scope, or exploit status. For a possible software exposure, identify the exact dependency version and whether sensitive code paths ran. For MCP, consider not only which tools can execute but also which server descriptions enter model context and whether sensitive actions receive human review. For device or service advisories, consult the relevant vendor or project’s current guidance rather than inferring present status from a historical roundup.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
