In a sophisticated onslaught targeting the open-source ecosystem, reports have emerged detailing several malicious npm packages that are nefariously exploiting the Telegram Bot API to install backdoors on unsuspecting developers’ Linux systems.
This alarming trend has escalated concerns over the integrity of software supply chains, particularly in light of the platform’s open development architecture.
Cybercriminals Leverage Open Ecosystem for Malware Distribution
Telegram, with its burgeoning user base of over 1 billion monthly active users as of 2025, has become a prime target for cybercrime due to its bot-friendly environment.
.png
)
The ecosystem allows anyone to develop and deploy bots without a rigorous vetting process, making it ripe for exploitation.
Developers often rely on trusted libraries like node-telegram-bot-api, but attackers have introduced malicious packages with names similar to the legitimate one, such as node-telegram-utils, node-telegram-bots-api, and node-telegram-util, which have been quietly installing backdoors into systems.
Upon initialization, these malicious packages execute a function named addBotId(), which checks if the operating system is Linux.
If confirmed, the function proceeds to modify the developer’s SSH configuration, injecting two SSH public keys into the .ssh/authorized_keys file.
According to the Report, this manipulation provides attackers with persistent, passwordless access to the compromised system.
Developers might overlook these lines of code embedded within the broader context of an otherwise legitimate-looking library, thereby leaving their systems vulnerable to ongoing unauthorized access even after removing the package.
Data Exfiltration and Persistent Access Risks
The attackers do not stop at just gaining access; they also initiate data exfiltration.
Using APIs like ipinfo.io, the packages collect the external IP address and username of the system, sending this information back to a server disguised under a domain called solana[.]validator[.]blog.
This setup allows attackers to not only maintain persistence on compromised systems but also to gather valuable intelligence that could be used for further exploits or lateral movement within organizational networks.
The prevalence of these attacks underscores the need for heightened vigilance among developers.
Regular dependency audits and the adoption of automated scanning tools are now imperative to detect and neutralize such threats before they infiltrate production environments.
Tools like Socket’s GitHub app and CLI offer proactive security by monitoring dependencies in real-time and flagging malicious behaviors during npm installations or builds.
In response to the evolving tactics of attackers, developers and organizations are urged to integrate multiple layers of security into their development practices.
This includes not only real-time monitoring and scanning but also understanding the behavioral patterns of the software they integrate.
The recent attacks utilizing advanced obfuscation techniques emphasize the necessity of staying ahead of cybercriminals through continuous updates and security integrations.
This wave of supply chain attacks through npm not only threatens individual developers but poses significant risks to organizational security, highlighting the critical need for robust security protocols within the software development lifecycle.
Find this News Interesting! Follow us on Google News, LinkedIn, & X to Get Instant Updates!
