Open Source · · 1 day

proto-tinker-wc shipped Qix wallet drainer

proto-tinker-wc 0.1.87 was reported with the same September 2025 npm wallet-drainer campaign. The malicious npm release put browser-side transaction manipulation code into a legitimate package path.

Part of Qix phishing shipped wallet drainers campaign

proto-tinker-wc was a small follow-on artifact in a much larger September 2025 npm compromise. Public reporting and ecosystem advisories tied version 0.1.87 to the same phishing-driven wallet-drainer campaign that first surfaced through Qix-maintained packages.

The package is recorded separately because its maintainer and distribution surface differ from Qix, DuckDB, Prebid, and CoveOps. That distinction matters for responders: each package name creates a different lockfile query, cache check, and owner notification path.

The malicious release put browser-side transaction-manipulation code into a legitimate npm package path. In the Qix campaign, that family watched wallet and web3 activity and attempted to redirect transaction destinations to attacker-controlled addresses.

This page preserves the proto-tinker-wc package coordinate, version, hash, and September 9 exposure date. The parent [[qix-npm-phishing-2025]] record carries the shared phishing infrastructure, wallet-drainer behavior, and cross-package timing.

Notes

  • An indicator recorded here gave the SHA-256 of a zero-byte file as the digest of the compromised tarball, so a failed or empty download had been recorded as evidence. It has been removed. The digest on the artifact itself is unaffected.

Appendix · Affected releases

References

  1. New compromised packages identified in largest npm attack in historyjfrog.com
  2. Qix npm package supply chain compromisethreats.wiz.io
  3. Malicious code in proto-tinker-wcosv.dev
  4. Embedded Malicious Code in proto-tinker-wcsecurity.snyk.io

Source record: oss/attacks/proto-tinker-wc/meta.yaml