mal-2026-3287
Vulnerability from ossf_malicious_packages
Published
2026-05-02 08:00
Modified
2026-05-02 08:00
Summary
Malicious code in ams-ssk (npm)
Details

Malicious npm package published by user shetty123 as part of a Telegram account hijacking framework targeting Indian Telegram users. All 31 published versions (1.0.0 through 1.0.33) are malicious. Pairs with common-tg-service, which performs the client-side Telegram account takeover.

ams-ssk is the server-side AMS/CMS infrastructure for the operation. It exposes a file-management CRUD API including a bulk-zip download endpoint (folders/:folder/files/download-all) and a multi-bot Telegram message-forwarder with per-bot operation counters used to fan out hijacked-account traffic. Observed deployments include cms.paidgirl.site and promoteClients2.glitch.me. The package is part of an actor-controlled stack (operator identity shetty123 / display name Mad_man) used to manage stolen Telegram accounts and exfiltrate data to attacker-controlled Telegram channels (-1001801844217, -1001972065816).

Malice executes at runtime when the service is initialized; there are no preinstall/postinstall lifecycle scripts, so the package bypasses install-time scanners.

Credits
SafeDep safedep.io

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "ams-ssk"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "SEMVER"
        }
      ]
    }
  ],
  "credits": [
    {
      "contact": [
        "https://safedep.io"
      ],
      "name": "SafeDep",
      "type": "FINDER"
    }
  ],
  "database_specific": {
    "malicious-packages-origins": null
  },
  "details": "Malicious npm package published by user `shetty123` as part of a Telegram account hijacking framework targeting Indian Telegram users. All 31 published versions (1.0.0 through 1.0.33) are malicious. Pairs with `common-tg-service`, which performs the client-side Telegram account takeover.\n\n`ams-ssk` is the server-side AMS/CMS infrastructure for the operation. It exposes a file-management CRUD API including a bulk-zip download endpoint (`folders/:folder/files/download-all`) and a multi-bot Telegram message-forwarder with per-bot operation counters used to fan out hijacked-account traffic. Observed deployments include `cms.paidgirl.site` and `promoteClients2.glitch.me`. The package is part of an actor-controlled stack (operator identity `shetty123` / display name `Mad_man`) used to manage stolen Telegram accounts and exfiltrate data to attacker-controlled Telegram channels (`-1001801844217`, `-1001972065816`).\n\nMalice executes at runtime when the service is initialized; there are no preinstall/postinstall lifecycle scripts, so the package bypasses install-time scanners.",
  "id": "MAL-2026-3287",
  "modified": "2026-05-02T08:00:00Z",
  "published": "2026-05-02T08:00:00Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://safedep.io/malicious-common-tg-service-npm-telegram-hijacking-framework/"
    }
  ],
  "schema_version": "1.7.4",
  "summary": "Malicious code in ams-ssk (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…