tipsen-last-plsnpm
tipsen-last-pls is a confirmed malicious npm package (MAL-2026-10392) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tipsen-last-pls (npm)
What this malware does
package.json declares a dependency safe-chain-test whose version specifier is a direct HTTPS tarball URL on an anonymous Cloudflare ephemeral tunnel: https://harris-encourage-westminster-political.trycloudflare.com/safe-chain-test-1.0.0.tgz. On npm install, npm fetches and installs the tarball from this non-registry, mutable, non-publisher-owned host and runs any lifecycle scripts inside it. The tarball is not pinned by integrity hash, is not hosted on the npm registry or a publisher-owned domain, and its contents are entirely controlled by whoever operates the tunnel — enabling arbitrary code execution on the installer's machine at install time. The manifest self-describes as 'Safe Chain transitive tarball scanning reproduction' and ships no code of its own (declared main: index.js is absent), so the package's sole effect on install is to resolve and execute the tunnel-hosted dependency.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tipsen-last-pls (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tipsen-last-pls across your stack and pipelines.
If you installed it — respond
Remove tipsen-last-pls from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If tipsen-last-pls was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks tipsen-last-pls before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks tipsen-last-pls-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.