@nuri.yavuz.tr.2/my-unique-pingernpm
Advisory published Updated
@nuri.yavuz.tr.2/my-unique-pinger is a confirmed malicious npm package (MAL-2026-18716) that executes malicious code on install (malicious version 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @nuri.yavuz.tr.2/my-unique-pinger (npm)
What this malware does
The OpenSSF Package Analysis project identified '@nuri.yavuz.tr.2/my-unique-pinger' @ 1.0.2 (npm) as malicious.
It is considered malicious because:
- The package executes one or more commands associated with malicious behavior.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for @nuri.yavuz.tr.2/my-unique-pinger (version 1.0.2).
If you installed it — respond
Remove @nuri.yavuz.tr.2/my-unique-pinger 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 @nuri.yavuz.tr.2/my-unique-pinger was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Credits
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks @nuri.yavuz.tr.2/my-unique-pinger-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.