Last updated: August 19, 2026 at 1:47 AM UTC
All 741 Vulnerability 286 Breach 129 Threat 319 Defense 7
Tag: crypto-wallet (5 articles)Clear

SafePal order-tracking flaw exposed data of nearly 40,000 wallet buyers

Cryptocurrency wallet maker SafePal disclosed that an authorization flaw in a third-party order-tracking plug-in exposed personal data of about 39,798 customers, and a threat actor is now selling it. The flaw worked like a parcel tracker that lets one customer see another's order simply by changing the order number, exposing names, email addresses, shipping addresses, phone numbers, and purchase details for orders placed between March 2025 and April 2026. Seed phrases, private keys, wallet passwords, and payment data were not affected. SafePal warned customers to expect phishing and impersonation, and noted that a fake firmware-update lure had already been seen. It has taken down more than 30 fraudulent sites.

Check
Affected SafePal customers should be alert to phishing and calls impersonating the company, never enter a seed phrase or approve a firmware update prompted by an unsolicited message, and verify notices independently.
Affected
About 39,798 SafePal customers whose names, emails, phone numbers, and shipping addresses were exposed; wallets and keys are safe, but the data supports convincing phishing, including fake firmware-update scams already observed.
Fix
Anyone who shared a seed phrase or keys through a scam should move funds to a new wallet now; organizations should audit third-party plug-ins for authorization flaws limiting customer data.

OkoBot malware injects fake seed-phrase prompts into real Ledger and Trezor apps

Kaspersky detailed OkoBot, a Windows malware framework active since 2025 whose standout module, SeedHunter, tricks hardware-wallet owners into giving up their recovery phrase. On an infected PC, the malware waits for wallet software like Ledger Live, Ledger Wallet, or Trezor Suite, sometimes until the device is plugged in, then displays a malicious page asking for the seed phrase from inside the wallet's own genuine app. Because the surrounding application is the real one the victim installed, the request looks legitimate, but anyone who types in the phrase hands over full control of their funds. Kaspersky counted hundreds of victims across more than 25 countries, and the framework remains active.

Check
Remind cryptocurrency users that hardware wallets never ask for the recovery phrase to be typed into a computer, and any prompt requesting it, even inside the real wallet app, is a scam.
Affected
Hardware-wallet owners on OkoBot-infected Windows PCs; the malware injects a fake recovery-phrase request into the genuine Ledger or Trezor desktop app, and victims who enter the phrase lose control of their cryptocurrency.
Fix
Never enter a wallet recovery phrase into any computer prompt, keep endpoints protected to catch OkoBot, and confirm sensitive actions on the hardware device's own screen rather than the desktop app.

Compromised Injective npm SDK stole crypto wallet keys from developers' apps

Attackers compromised a legitimate maintainer's GitHub account for the Injective blockchain SDK and used it to push a malicious version of the widely used @injectivelabs/sdk-ts npm package, which has around 50,000 weekly downloads. The tainted code, disguised as usage telemetry, hooked the SDK's wallet key-generation functions to capture private keys and seed phrases, then sent them to a server made to look like legitimate Injective infrastructure. Trusted-publishing automation spread the malicious release across 18 packages within minutes, though it was live under an hour before being pulled. Because the theft can reach apps that used the SDK only indirectly, any wallet keys handled by affected versions should be treated as compromised.

Check
Check whether your projects or dependencies pulled the malicious Injective SDK version, including transitive dependencies and cached copies, and review whether any wallet keys or seed phrases passed through affected code.
Affected
Developers and applications using the affected @injectivelabs/sdk-ts versions, and their users; the malware captured wallet private keys and seed phrases, even for apps that depended on the SDK only indirectly.
Fix
Move any potentially exposed cryptocurrency to fresh wallets, rotate secrets in affected environments, pin dependencies to known-good versions, and protect maintainer accounts and publishing pipelines with phishing-resistant MFA.

Kaspersky finds 26 'FakeWallet' apps on Apple's App Store impersonating MetaMask, Coinbase, Trust Wallet, and Ledger to steal crypto seed phrases

Kaspersky identified 26 malicious iOS apps live on the Apple App Store impersonating major cryptocurrency wallets including MetaMask, Coinbase, Trust Wallet, Ledger, TokenPocket, imToken, Bitpie, and OneKey. The campaign, named FakeWallet and linked to the SparkKitty operation, has been running since fall 2025. The apps used typosquatted names, cloned icons, and stub functionality (games, calculators, task planners) to pass App Store review. Some embed compromised viewDidLoad routines that scan the screen for mnemonic words as the user types and exfiltrate seed phrases via RSA-encrypted payloads. Apple removed 25 of the 26 after disclosure; the developer behind the 26th was terminated.

Check
Audit wallet apps installed on any iOS device that holds crypto credentials - your own and team members' devices used for treasury, payroll, vendor payments, or personal investing.
Affected
iOS users who downloaded any of the 26 FakeWallet apps between fall 2025 and the April 2026 takedowns, particularly those with Apple account region set to China. Anyone who entered a seed phrase must assume their wallet is compromised. Cold wallet users are not exempt - some variants embedded into companion apps.
Fix
Review every App Store download under any region, particularly wallet or crypto apps. Cross-check developer names against official wallet websites (MetaMask is ConsenSys, Trust Wallet is DApps Platform Inc., Ledger is Ledger SAS). Any wallet app that asks for your seed phrase is a thief. If exposed, transfer assets to a fresh wallet on known-clean hardware and treat the old seed as burned.

Self-propagating npm worm hits Namastex Labs packages, steals secrets across npm, PyPI, and crypto wallets

A new supply-chain worm is loose on npm, stealing developer credentials and republishing itself automatically from whichever compromised account it lands on. Socket and StepSecurity identified the attack in packages published by Namastex Labs, a company that builds agentic AI tooling, with 16 package versions confirmed malicious so far and the first poisoned release (pgserve 1.1.11 on April 21 at 22:14 UTC) followed by two more the same day. The injected code grabs tokens, API keys, SSH keys, credentials for cloud services, CI/CD systems, container registries, and LLM platforms, plus Kubernetes and Docker configs, then rifles through Chrome and Firefox for cryptocurrency wallet data including MetaMask, Exodus, Atomic Wallet, and Phantom. If the malware finds an npm publish token in environment variables or ~/.npmrc, it identifies every package the victim can publish, injects itself into each, bumps the version, and republishes - a worm in the literal sense. It applies the same trick to PyPI via a .pth-based payload if Python credentials are present, making this a cross-ecosystem threat. Socket and StepSecurity note the techniques mirror TeamPCP's CanisterWorm attacks but stop short of definitive attribution.

Check
Search your package-lock and yarn.lock files and private registry caches for any of the listed Namastex Labs versions, and then rotate every credential that has ever been present on a machine that installed them.
Affected
Confirmed malicious versions per Socket: @automagik/genie 4.260421.33 through 4.260421.39; pgserve 1.1.11 through 1.1.13; @fairwords/websocket 1.0.38 through 1.0.39; @fairwords/loopback-connector-es 1.4.3 through 1.4.4; @openwebconcept/theme-owc 1.0.3; @openwebconcept/design-tokens 1.0.3. Any additional npm package republished by an account whose publish token was exfiltrated by this worm is also potentially malicious.
Fix
Remove the listed versions from development environments, CI/CD runners, and private mirrors immediately. Rotate every secret the worm would have seen: npm publish tokens, PyPI tokens, cloud provider keys, CI/CD deploy keys, SSH keys, LLM platform API keys, container registry credentials, and any crypto wallet seeds stored in browser extensions on affected machines. Audit your package caches and internal mirrors for related packages that share the same public.pem file, webhook host, or postinstall pattern (Socket publishes IoCs for this). Pin production dependencies to known-good versions with integrity hashes and deny the newest versions of the affected packages in your package firewall until forensics is complete.