MalwarePublished 31 Oct 2025

sabay-tg-api (npm) · Malicious Code

Affects sabay-tg-apiSource GCVE Database

Malicious package : remove sabay-tg-api and rotate any secrets on hosts that installed it.

Data as of 29 Oct 2026, 23:26 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-49266

What to do

Remove sabay-tg-api 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
npmsabay-tg-api	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 sabay-tg-api contains malicious code that compromises any computer on which it is installed or running. Systems with this package should be considered fully compromised, and all secrets and keys stored on those systems must be rotated immediately from a different, trusted computer. Removing the package alone does not guarantee the removal of all malicious software introduced by it.

Impact

Any computer with the sabay-tg-api package installed or running is considered fully compromised, potentially allowing attackers full control over the system. This includes the risk of exposure or theft of all stored secrets and keys. The compromise is severe enough that simply uninstalling the package does not guarantee complete removal of malicious components.

Defensive guidance

Immediately remove the sabay-tg-api package from affected systems. Rotate all secrets and keys stored on compromised systems from a separate, trusted computer. Conduct a thorough investigation and remediation to identify and remove any additional malicious software or backdoors that may have been installed. Monitor for any signs of persistent compromise.

Summary

The sabay-tg-api npm package has been identified as containing malicious code. Installation or execution of this package results in a full compromise of the affected system. Due to the severity of the compromise, all secrets and keys stored on the system should be rotated from a separate, secure environment. The package removal is necessary but insufficient to fully remediate the infection, as the attacker may have established persistent control beyond the package itself.

References

github.com/advisories/GHSA-g9ch-qvf6-jgfj (opens in a new tab)

Community reviews

Loading reviews…

What to do

Affected software

Description

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

Technical details

References

Community reviews