paper-password-inputnpm
paper-password-input is a confirmed malicious npm package (MAL-2026-15542) that executes malicious code on install (malicious version 45.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in paper-password-input (npm)
What this malware does
package.json declares a dependency whose key equals the package's own name (paper-password-input) and whose value is a bare HTTPS URL, https://repo.securityctrl.com/paper-password-input, rather than a registry version range. On npm install, npm fetches whatever bytes are served at that URL with no version pin and no integrity check, and executes any lifecycle scripts inside the fetched tarball. The shipped index.js is an inert stub, so the manifest itself is the entire published surface — whoever controls repo.securityctrl.com can deliver arbitrary code to every installer, and the self-named dependency shape is consistent with a dependency-confusion lure targeting an internal package name.
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 paper-password-input (version 45.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging paper-password-input across your stack and pipelines.
If you installed it — respond
Remove paper-password-input 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 paper-password-input 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 paper-password-input 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 paper-password-input-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.