@pisell/pisellos@2.2.168
Malicious code in @pisell/pisellos (npm)
Analysis
Critical maintainer_change finding: email changed from [account] to [account]. Package has prepublishOnly lifecycle hook (runs npm run build - benign). Investigation found no token-theft markers. The eval() usage in lib/plugins/window.js is legitimate - it's a mock browser setTimeout/setInterval implementation for a sandboxed environment SDK. Package appears to be a frontend modular SDK framework. However, repository URL uses generic 'username' placeholder (github[.]com/username/pisell-os), and I cannot independently verify the publisher identity transition. Given Critical severity and inability to fully confirm this is a legitimate corporate email migration vs. account takeover, recommending human review.
- analyzed by
- Leitwacht
- first seen
- May 26, 2026, 02:25 PM
- analyzed
- May 26, 2026, 06:37 PM
- weekly installs
- 4,914
Related advisories
- @pisell/pisellos@2.2.172 same package
- @pisell/pisellos@2.2.164 same package
- @pisell/pisellos@2.2.169 same package
- @pisell/pisellos@2.2.173 same package
- statist-browser-typed-client-fsi.cm.web@0.0.1
- statist-browser-typed-client-forge.informer.events@0.0.1
- statist-browser-typed-client-forge.front.metrics@0.0.1
- statist-browser-typed-client-eventea.spend.advisor@0.0.1
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.