Which versions of ams-ssk are malicious?

Every published version of ams-ssk on npm is considered malicious. Remove the package entirely.

How do I remediate ams-ssk if I installed it?

ams-ssk is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed ams-ssk — how do I know if it already compromised me?

If ams-ssk was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is ams-ssk part of a known attack campaign?

Yes — ams-ssk is associated with the GHSA-827p-whjw-xp3w campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find ams-ssk across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ams-ssk (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ams-ssk across your stack and pipelines.

Malicious package

ams-ssknpm

ams-ssk is a confirmed malicious npm package (MAL-2026-3287) that steals credentials and exfiltrates sensitive data. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ams-ssk (npm)

MAL-2026-3287

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall ams-ssk

What this malware does

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.

The package ams-ssk was found to contain malicious code.

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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

89bf12be8e3ded6d209b121dd7538d92b8623e501512b2505ac402e76367ad3b

ab6ebeb3c1aad1f0ed18ca0a596ad66ccc049a8d5cc09e1dc8b06c8bce14bf61

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ams-ssk (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ams-ssk across your stack and pipelines.
If you installed it — respond
ams-ssk is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If ams-ssk was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks ams-ssk before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. ams-ssk on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-827p-whjw-xp3w

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks ams-ssk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database