mal-2026-3509
Vulnerability from ossf_malicious_packages
Published
2026-05-11 00:00
Modified
2026-05-13 08:31
Summary
Malicious code in pp-react-v5 (npm)
Details

pp-react-v5 is a dependency confusion package published at the inflated version 10.0.0 to win npm resolution over any internally-hosted package of the same name. The package contains only a package.json with no functional source code.

On installation the preinstall script executes a wget command that sends a GET request to http://q9ou9xtw.requestrepo.com/ with the current username (whoami), working directory (pwd), and hostname as query parameters, beaconing the victim machine's identity to the attacker-controlled endpoint.


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

Source: amazon-inspector (667950ffe2ed24a98495c0d8d6c3430e3538523c5811caf9fbda829b0773163f)

The package pp-react-v5 was found to contain malicious code.

Source: ossf-package-analysis (b2291adfbdded958f2fa2a51aa5e582d8ec4bad5bb1c5c9b614bd496732c3578)

The OpenSSF Package Analysis project identified 'pp-react-v5' @ 10.0.0 (npm) as malicious.

It is considered malicious because:

  • The package executes one or more commands associated with malicious behavior.

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "pp-react-v5"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "versions": [
        "10.0.0"
      ]
    }
  ],
  "credits": [
    {
      "contact": [
        "actran@amazon.com"
      ],
      "name": "Amazon Inspector",
      "type": "FINDER"
    },
    {
      "contact": [
        "https://github.com/ossf/package-analysis",
        "https://openssf.slack.com/channels/package_analysis"
      ],
      "name": "OpenSSF: Package Analysis",
      "type": "FINDER"
    },
    {
      "contact": [
        "https://safedep.io"
      ],
      "name": "SafeDep",
      "type": "FINDER"
    }
  ],
  "database_specific": {
    "malicious-packages-origins": [
      {
        "import_time": "2026-05-12T01:40:23.98730387Z",
        "modified_time": "2026-05-11T11:20:56Z",
        "sha256": "b2291adfbdded958f2fa2a51aa5e582d8ec4bad5bb1c5c9b614bd496732c3578",
        "source": "ossf-package-analysis",
        "versions": [
          "10.0.0"
        ]
      },
      {
        "import_time": "2026-05-12T07:28:55.481363286Z",
        "modified_time": "2026-05-12T06:53:21Z",
        "sha256": "667950ffe2ed24a98495c0d8d6c3430e3538523c5811caf9fbda829b0773163f",
        "source": "amazon-inspector",
        "versions": [
          "10.0.0"
        ]
      }
    ]
  },
  "details": "`pp-react-v5` is a dependency confusion package published at the inflated version `10.0.0` to win npm resolution over any internally-hosted package of the same name. The package contains only a `package.json` with no functional source code.\n\nOn installation the `preinstall` script executes a `wget` command that sends a GET request to `http://q9ou9xtw.requestrepo.com/` with the current username (`whoami`), working directory (`pwd`), and hostname as query parameters, beaconing the victim machine\u0027s identity to the attacker-controlled endpoint.\n\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (667950ffe2ed24a98495c0d8d6c3430e3538523c5811caf9fbda829b0773163f)\nThe package pp-react-v5 was found to contain malicious code.\n\n## Source: ossf-package-analysis (b2291adfbdded958f2fa2a51aa5e582d8ec4bad5bb1c5c9b614bd496732c3578)\nThe OpenSSF Package Analysis project identified \u0027pp-react-v5\u0027 @ 10.0.0 (npm) as malicious.\n\nIt is considered malicious because:\n\n- The package executes one or more commands associated with malicious behavior.\n",
  "id": "MAL-2026-3509",
  "modified": "2026-05-13T08:31:58Z",
  "published": "2026-05-11T00:00:00Z",
  "schema_version": "1.7.4",
  "summary": "Malicious code in pp-react-v5 (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…