Vulnerabilities in pkg:npm/simple-swizzle

PACKAGE
Advisory Identifier: GHSA-9g9j-rggx-7fmg
Advisory Summary

CVE-2025-59141 is a HIGH simple-swizzle@0.2.3 contains malware after npm vulnerability (CWE-506: Embedded Malicious Code) affecting Simple swizzle libraries in the npm ecosystem. The issue involves simple-swizzle@0.2.3 contains malware after npm account takeover. Remediation is available by upgrading affected packages to version 0.2.4.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/simple-swizzle

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/simple-swizzle. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-9g9j-rggx-7fmg CVE-2025-59141 HIGH simple-swizzle@0.2.3 contains malware after npm account takeover

CVE-2025-59141 at a Glance

CVE Identifier CVE-2025-59141
GHSA Identifier GHSA-9g9j-rggx-7fmg
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-506: Embedded Malicious Code
Affected Product Simple swizzle
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2025-59141

To remediate this vulnerability, upgrade all affected Simple swizzle dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

simple-swizzle fixed: 0.2.4
npm install simple-swizzle@0.2.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls simple-swizzle

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2025-59141, inspect your project dependencies using npm:

npm ls simple-swizzle

Analyze the terminal output to locate any version of Simple swizzle in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.2.4), your application is affected.

Note: The npm ls simple-swizzle command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-506: Embedded Malicious Code, where the product contains code that appears to be malicious in nature. In Simple swizzle, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact On 8 September 2025, the npm publishing account for `simple-swizzle` was taken over after a phishing attack. Version `0.2.3` was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker's own addresses from within browser environments. Local environments, server environments, command line applications, etc. are not affected. If the package was used in a browser context (e.g. a direct `<script>` inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt. The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask. See references below for more information on the payload. ### Patches npm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper. On 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached. This version is functionally identical to the previously known-good version, published as a patch version bump above the compromised version. Users should update to the latest patch version, completely remove their `node_modules` directory, clean their package manager's global cache, and rebuild any browser bundles from scratch. Those operating private registries or registry mirrors should purge the offending versions from any caches. ### References - https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised - https://socket.dev/blog/npm-author-qix-compromised-in-major-supply-chain-attack - https://www.ox.security/blog/npm-packages-compromised/ ### Point of Contact In the event suspicious behavior is still observed for the package listed in this security advisory after performing all of the above cleaning operations (see _Patches_ above), please reach out via one of the following channels of communication: - Bluesky, package owner: https://bsky.app/profile/bad-at-computer.bsky.social - `debug` repository, tracking issue (applies to all packages affected in the breach): https://github.com/debug-js/debug/issues/1005

CVE-2025-59141 Affected Simple swizzle Versions

1 component(s)
Fixed Versions:
0.2.4
Product / Package Ecosystem Affected Versions Fixed Version
simple-swizzle
npm
≥ 0.2.3
< 0.2.4
All 1 versions
0.2.3
0.2.4

References

Frequently Asked Questions

What is CVE-2025-59141?
CVE-2025-59141 is a security vulnerability in Simple swizzle involving simple-swizzle@0.2.3 contains malware after npm account takeover under CWE-506: Embedded Malicious Code.
Which Simple swizzle versions are affected?
Affected versions include releases prior to 0.2.4 across affected packages: simple-swizzle.
What version fixes CVE-2025-59141?
Upgrading to 0.2.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is simple-swizzle affected?
Yes, simple-swizzle is affected in releases prior to 0.2.4. Upgrade your dependency to 0.2.4 or later.
What CWE is associated with CVE-2025-59141?
CVE-2025-59141 is classified under CWE-506: Embedded Malicious Code (The product contains code that appears to be malicious in nature.).
How can I check npm dependencies for CVE-2025-59141?
Run the dependency tree command: 'npm ls simple-swizzle'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-9g9j-rggx-7fmg",
  "modified" : "2025-09-15T21:59:00Z",
  "published" : "2025-09-15T21:22:55Z",
  "aliases" : [ "CVE-2025-59141" ],
  "summary" : "simple-swizzle@0.2.3 contains malware after npm account takeover",
  "details" : "### Impact\nOn 8 September 2025, the npm publishing account for `simple-swizzle` was taken over after a phishing attack. Version `0.2.3` was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker's own addresses from within browser environments.\n\nLocal environments, server environments, command line applications, etc. are not affected. If the package was used in a browser context (e.g. a direct `<script>` inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt.\n\nThe malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask. See references below for more information on the payload.\n\n### Patches\nnpm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper.\n\nOn 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached. This version is functionally identical to the previously known-good version, published as a patch version bump above the compromised version.\n\nUsers should update to the latest patch version, completely remove their `node_modules` directory, clean their package manager's global cache, and rebuild any browser bundles from scratch.\n\nThose operating private registries or registry mirrors should purge the offending versions from any caches.\n\n### References\n- https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised\n- https://socket.dev/blog/npm-author-qix-compromised-in-major-supply-chain-attack\n- https://www.ox.security/blog/npm-packages-compromised/\n\n### Point of Contact\nIn the event suspicious behavior is still observed for the package listed in this security advisory after performing all of the above cleaning operations (see _Patches_ above), please reach out via one of the following channels of communication:\n\n- Bluesky, package owner: https://bsky.app/profile/bad-at-computer.bsky.social\n- `debug` repository, tracking issue (applies to all packages affected in the breach): https://github.com/debug-js/debug/issues/1005",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N/E:A/U:Red"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "simple-swizzle"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.2.3"
      }, {
        "fixed" : "0.2.4"
      } ]
    } ],
    "versions" : [ "0.2.3" ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/Qix-/node-simple-swizzle/security/advisories/GHSA-9g9j-rggx-7fmg"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-59141"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/debug-js/debug/issues/1005"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/Qix-/node-simple-swizzle"
  }, {
    "type" : "WEB",
    "url" : "https://socket.dev/blog/npm-author-qix-compromised-in-major-supply-chain-attack"
  }, {
    "type" : "WEB",
    "url" : "https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised"
  }, {
    "type" : "WEB",
    "url" : "https://www.ox.security/blog/npm-packages-compromised"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-506" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-09-15T21:22:55Z",
    "nvd_published_at" : "2025-09-15T20:15:38Z"
  }
}