mal-2026-6677
Vulnerability from ossf_malicious_packages
Published
2026-06-30 14:10
Modified
2026-07-01 19:13
Summary
Malicious code in ts-lint-builders-v2.1 (npm)
Details

-= Per source details. Do not edit below this line.=-

Source: amazon-inspector (7fc4c23edadea0930347028a24b67219dad6d3cbc4ec0fe1f93e8954425107ad)

On npm install, the package's postinstall hook (node test.js) executes a multi-stage attack against the installer. (1) It recursively scans the current working directory for files matching id.json (Solana keypair files), config.toml/Config.toml, .env, and env, and POSTs each match with the OS username to https://datasecure-service.vercel.app/api/v1. (2) It fetches an attacker-controlled pattern list from https://datasecure-service.vercel.app/api/scan-patterns, then enumerates the user's home directory on Unix (and non-C drives plus C:\Users on Windows via wmic logicaldisk get name), bulk-uploading matched files via multipart form to https://datasecure-service.vercel.app/api. (3) On Linux, it retrieves an SSH public key from https://datasecure-service.vercel.app/api/ssh-key, appends it to ~/.ssh/authorized_keys, and runs sudo chown plus sudo ufw enable and sudo ufw allow 22/tcp to ensure inbound SSH access — establishing persistent attacker access. The package name impersonates lint tooling but implements no linter functionality, and declares Node built-ins child_process and os as npm dependencies — typosquat lures pulling additional registry packages. This is a credential-stealer + persistent backdoor that fires automatically on install.

Source: ghsa-malware (f7a4f3654ba773deb07e8be2bbb938a4738587d26a4950da06e84b96f1925f33)

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

CWE
  • CWE-506 - The product contains code that appears to be malicious in nature.
  • CWE-506 - The product contains code that appears to be malicious in nature.
Credits

{
  "affected": [
    {
      "database_specific": {
        "cwes": [
          {
            "cweId": "CWE-506",
            "description": "The product contains code that appears to be malicious in nature.",
            "name": "Embedded Malicious Code"
          },
          {
            "cweId": "CWE-506",
            "description": "The product contains code that appears to be malicious in nature.",
            "name": "Embedded Malicious Code"
          }
        ],
        "indicators": {
          "evidence_files": [
            {
              "path": "index.js",
              "sha256": "5591dd6ad58a9351f98c415ff7be21fc4c71ac2a2862418c7e86f54c2cedc209",
              "tlsh": "a9f196d991772661cfb233b85a07100dfbdad13338028651b6ec46497f7b52861e2eee"
            },
            {
              "path": "package.json",
              "sha256": "42e4965b99a546a42dab8b51e4643c4fdcfbeea924366bcdb4bd5fdd4749fd2d",
              "tlsh": "98f0a926ca288e6718f126a829b80717f292832f0100880f35bd2b0c4fb66270486f2e"
            }
          ]
        }
      },
      "package": {
        "ecosystem": "npm",
        "name": "ts-lint-builders-v2.1"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "versions": [
        "2.1.0"
      ]
    }
  ],
  "aliases": [
    "GHSA-vjgf-xg3j-g9c5"
  ],
  "credits": [
    {
      "contact": [
        "inspector-research@amazon.com"
      ],
      "name": "Amazon Inspector",
      "type": "FINDER"
    }
  ],
  "database_specific": {
    "malicious-packages-origins": [
      {
        "id": "GHSA-vjgf-xg3j-g9c5",
        "import_time": "2026-06-30T15:09:17.668846899Z",
        "modified_time": "2026-06-30T14:10:18Z",
        "ranges": [
          {
            "events": [
              {
                "introduced": "0"
              }
            ],
            "type": "SEMVER"
          }
        ],
        "sha256": "f7a4f3654ba773deb07e8be2bbb938a4738587d26a4950da06e84b96f1925f33",
        "source": "ghsa-malware"
      },
      {
        "id": "IN-MAL-2026-007846",
        "import_time": "2026-07-01T19:11:23.280669039Z",
        "modified_time": "2026-07-01T18:35:03Z",
        "sha256": "7fc4c23edadea0930347028a24b67219dad6d3cbc4ec0fe1f93e8954425107ad",
        "source": "amazon-inspector",
        "versions": [
          "2.1.0"
        ]
      }
    ]
  },
  "details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (7fc4c23edadea0930347028a24b67219dad6d3cbc4ec0fe1f93e8954425107ad)\nOn `npm install`, the package\u0027s postinstall hook (`node test.js`) executes a multi-stage attack against the installer. (1) It recursively scans the current working directory for files matching `id.json` (Solana keypair files), `config.toml`/`Config.toml`, `.env`, and `env`, and POSTs each match with the OS username to https://datasecure-service.vercel.app/api/v1. (2) It fetches an attacker-controlled pattern list from https://datasecure-service.vercel.app/api/scan-patterns, then enumerates the user\u0027s home directory on Unix (and non-C drives plus C:\\Users on Windows via `wmic logicaldisk get name`), bulk-uploading matched files via multipart form to https://datasecure-service.vercel.app/api. (3) On Linux, it retrieves an SSH public key from https://datasecure-service.vercel.app/api/ssh-key, appends it to `~/.ssh/authorized_keys`, and runs `sudo chown` plus `sudo ufw enable` and `sudo ufw allow 22/tcp` to ensure inbound SSH access \u2014 establishing persistent attacker access. The package name impersonates lint tooling but implements no linter functionality, and declares Node built-ins `child_process` and `os` as npm dependencies \u2014 typosquat lures pulling additional registry packages. This is a credential-stealer + persistent backdoor that fires automatically on install.\n\n## Source: ghsa-malware (f7a4f3654ba773deb07e8be2bbb938a4738587d26a4950da06e84b96f1925f33)\nAny computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.\n",
  "id": "MAL-2026-6677",
  "modified": "2026-07-01T19:13:21Z",
  "published": "2026-06-30T14:10:13Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-vjgf-xg3j-g9c5"
    },
    {
      "type": "PACKAGE",
      "url": "https://www.npmjs.com/package/ts-lint-builders-v2.1/v/2.1.0"
    }
  ],
  "schema_version": "1.7.4",
  "summary": "Malicious code in ts-lint-builders-v2.1 (npm)"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…