MalwarePublished 31 Oct 2025

custom-tg-bot-plan (npm) · Malicious Code

Affects custom-tg-bot-planSource GCVE Database

Malicious package : remove custom-tg-bot-plan and rotate any secrets on hosts that installed it.

Data as of 29 Oct 2026, 23:25 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-49256

What to do

Remove custom-tg-bot-plan from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmcustom-tg-bot-plan	Affected–	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The npm package custom-tg-bot-plan contains malicious code that compromises any computer on which it is installed or running. Installation of this package may lead to full system compromise, including unauthorized access to secrets and keys stored on the affected machine. Immediate removal of the package and rotation of all secrets from a different, uncompromised computer is strongly advised.

Impact

Systems with the custom-tg-bot-plan package installed are at risk of full compromise. Attackers may gain complete control over the affected computer, leading to potential theft or misuse of sensitive information such as secrets and keys. This represents a critical security risk requiring immediate action.

Defensive guidance

Remove the custom-tg-bot-plan package immediately from all affected systems. Rotate all secrets and keys that were stored on the compromised machines from a separate, secure computer. Due to the likelihood of full system compromise, further forensic analysis and remediation may be necessary to ensure all malicious components are eradicated.

Summary

The npm package custom-tg-bot-plan has been identified as containing malicious code. According to sources including Amazon Inspector and GHSA malware advisories, any system with this package installed should be considered fully compromised. The malicious code potentially grants an attacker full control over the affected system, risking exposure of all stored secrets and keys. Removal of the package alone may not fully remediate the infection due to possible persistence mechanisms or additional malware installed as a result of the compromise.

References

github.com/advisories/GHSA-vw4q-wx74-9mp7 (opens in a new tab)

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2026, 23:25 UTC

Technical details

References

Community reviews