Malicious code in dotish (npm)
MAL-2026-14418 · GHSA-5xvx-37p2-x7j9
Published · Modified
Dependency scanning
Check whether dotish is in your codebase
Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.
Description
__
Source: amazon-inspector (d2ccb1a1f0c28d673323f0377c9e65232611641c9de3dbb97f92b17779660b20)
The package's postinstall lifecycle script auto-runs on npm install and reads the installer's current working directory .env file (typically containing API keys, database credentials, and cloud tokens), then POSTs the full file contents together with os.hostname() to a hardcoded Telegram Bot API endpoint. The destination URL is stored as a base64 literal and decoded at runtime to https://api.telegram.org/bot<redacted>/sendMessage (bot id 8406833247, chat id 5934680334). Variable names are shaped to obscure the network call, comments are written in Somali, and the outbound request is wrapped in a try/catch that swallows errors. The package presents itself as an env-var utility and does not disclose any of this behavior.
Source: ghsa-malware (8880beb0826c731c6357842a92e9c64ad4e917289f9794e014731a9202a2c9f4)
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.
References
Ready to move
Start Securing
Free, no credit card | First findings in minutes