another-poc-by-tipsennpm
another-poc-by-tipsen is a confirmed malicious npm package (MAL-2026-10283) 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 another-poc-by-tipsen (npm)
What this malware does
package.json declares a dependency safe-chain-test sourced from a tarball URL on an anonymous Cloudflare tunnel host (periods-parcel-pittsburgh-upgrading.trycloudflare.com) rather than the npm registry or a pinned git SHA. On npm install, npm fetches and installs whatever bytes that ephemeral, publisher-controlled host serves at the moment of resolution, bypassing registry scanning and integrity pinning. The tunnel operator can change the served bytes at any time, so the installer's dependency graph resolves to arbitrary, unverifiable code executed with the transitive package's install-time and require-time privileges. The package itself is otherwise empty (only package.json and README.md; declared main index.js is absent), so the sole effect of installing it is to pull in the tunnel-hosted tarball.
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 another-poc-by-tipsen (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 another-poc-by-tipsen across your stack and pipelines.
If you installed it — respond
Remove another-poc-by-tipsen 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 another-poc-by-tipsen 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 another-poc-by-tipsen 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 another-poc-by-tipsen-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.