MAL-2026-4709
Vulnerability from ossf_malicious_packages
Published
2026-05-20 02:14
Modified
2026-05-27 22:27
Summary
Malicious code in wallet-agent-ai-radix (npm)
Details

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

Source: amazon-inspector (60a953d7785091650f4f48e0b038e71ad79788102ffd652bff4bb0e8bf40ea21)

dist/agent.js contains a hardcoded Telegram Bot API endpoint (https://api.telegram.org) reached via fetch() with a POST body that includes values from process.env. The bundle co-references wallet-related endpoints (api.astrolescent.com) alongside the Telegram exfiltration channel. A package whose advertised purpose is wallet/agent functionality has no legitimate reason to POST environment data or wallet context to a hardcoded third-party Telegram bot — this is the canonical hardcoded-C2 exfiltration shape, where any installer/operator running this package leaks data to the attacker who controls the embedded bot token.

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": {
          "evidence_files": [
            {
              "path": "dist/agent.js",
              "sha256": "eb69aab5eb9be86ff5c6bc8eec20eb220f532a5dffbd2dd409856c035815a78e",
              "tlsh": "adf161365af5786038a3d18ca73b4007b4b9ba13740ce464b78cf1a56fdc12945f2abd"
            }
          ],
          "package_integrity": [
            {
              "filename": "wallet-agent-ai-radix-1.0.0.tgz",
              "hashes": {
                "sha1": "a4bbcba20810d0f8a6a24b379309c8bad31f090d",
                "sha512_sri": "sha512-jpzkOg3RsFKQVIo7d3cvqBvfElaoz6dfSQy4cdE6R4c+vj1X5GsxVrv3aEMXozF0nolszY2ScUqj0l9ABdTAsg=="
              }
            }
          ]
        }
      },
      "package": {
        "ecosystem": "npm",
        "name": "wallet-agent-ai-radix"
      },
      "versions": [
        "1.0.0"
      ]
    }
  ],
  "credits": [
    {
      "contact": [
        "actran@amazon.com"
      ],
      "name": "Amazon Inspector",
      "type": "FINDER"
    }
  ],
  "database_specific": {
    "malicious-packages-origins": [
      {
        "id": "IN-MAL-2026-003400",
        "import_time": "2026-05-26T05:50:34.385556207Z",
        "modified_time": "2026-05-20T02:14:19Z",
        "sha256": "60a953d7785091650f4f48e0b038e71ad79788102ffd652bff4bb0e8bf40ea21",
        "source": "amazon-inspector",
        "versions": [
          "1.0.0"
        ]
      }
    ]
  },
  "details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (60a953d7785091650f4f48e0b038e71ad79788102ffd652bff4bb0e8bf40ea21)\ndist/agent.js contains a hardcoded Telegram Bot API endpoint (https://api.telegram.org) reached via fetch() with a POST body that includes values from process.env. The bundle co-references wallet-related endpoints (api.astrolescent.com) alongside the Telegram exfiltration channel. A package whose advertised purpose is wallet/agent functionality has no legitimate reason to POST environment data or wallet context to a hardcoded third-party Telegram bot \u2014 this is the canonical hardcoded-C2 exfiltration shape, where any installer/operator running this package leaks data to the attacker who controls the embedded bot token.\n",
  "id": "MAL-2026-4709",
  "modified": "2026-05-27T22:27:00Z",
  "published": "2026-05-20T02:14:19Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://www.npmjs.com/package/wallet-agent-ai-radix/v/1.0.0"
    }
  ],
  "schema_version": "1.7.4",
  "summary": "Malicious code in wallet-agent-ai-radix (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…