my-skibidi (npm) · Malicious Code
Affects my-skibidiSource GCVE Database
Malicious package : remove my-skibidi and rotate any secrets on hosts that installed it.
Data as of 26 Oct 2026, 16:22 UTC
Malicious package
Published to npm · OSV MAL-2026-17217
What to do
Remove my-skibidi 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 |
|---|---|---|
| npmmy-skibidi | 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 my-skibidi (versions 1.0.0 through 1.1.6) contains malicious code that unconditionally sends users' browser cookies to a hardcoded external server. This exfiltration occurs immediately upon loading the module without user consent or configuration options. The package's declared functionality does not require cookie access or transmission. Any application bundling this package risks leaking session data to an unauthorized third party. Removal of the package is recommended, but full system compromise is possible, necessitating secret and key rotation from a clean environment.
References
- github.com/advisories/GHSA-w4g6-rgx4-2wjf (opens in a new tab)
- npmjs.com/package/my-skibidi/v/1.0.2 (opens in a new tab)
- npmjs.com/package/my-skibidi/v/1.0.0 (opens in a new tab)
- npmjs.com/package/my-skibidi/v/1.0.3 (opens in a new tab)
- npmjs.com/package/my-skibidi/v/1.1.5 (opens in a new tab)
- npmjs.com/package/my-skibidi/v/1.1.2 (opens in a new tab)
- npmjs.com/package/my-skibidi/v/1.1.6 (opens in a new tab)
- npmjs.com/package/my-skibidi/v/1.1.1 (opens in a new tab)
- npmjs.com/package/my-skibidi/v/1.1.4 (opens in a new tab)
- npmjs.com/package/my-skibidi/v/1.1.3 (opens in a new tab)