express-session-timer (npm) · Malicious Code
Affects express-session-timerSource GCVE Database
Malicious package : remove express-session-timer and rotate any secrets on hosts that installed it.
Data as of 30 Sep 2026, 16:39 UTC
Malicious package
Published to npm · OSV MAL-2026-16065
What to do
Remove express-session-timer 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 |
|---|---|---|
| npmexpress-session-timer | 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 express-session-timer versions 1.0.0, 1.0.1, 1.0.11, 1.0.13, 1.0.14, 1.0.15, and 1.0.16 contains malicious code that triggers destructive behavior immediately upon being imported. Approximately 18 seconds after requiring the module, it recursively deletes the <cwd>/src directory and forcibly terminates Node.js processes related to the current working directory. This destructive routine occurs without any user configuration or opt-in and is unrelated to the package's advertised functionality. The package also depends on express-timer pinned to a security-hold placeholder version, indicating prior takedown activity. No patch or remediation information is provided.
References
- npmjs.com/package/express-session-timer/v/1.0.0 (opens in a new tab)
- npmjs.com/package/express-session-timer/v/1.0.1 (opens in a new tab)
- npmjs.com/package/express-session-timer/v/1.0.13 (opens in a new tab)
- npmjs.com/package/express-session-timer/v/1.0.14 (opens in a new tab)
- npmjs.com/package/express-session-timer/v/1.0.16 (opens in a new tab)
- npmjs.com/package/express-session-timer/v/1.0.11 (opens in a new tab)
- npmjs.com/package/express-session-timer/v/1.0.15 (opens in a new tab)