dependent-finalnpm
Advisory published Updated
dependent-final is a confirmed malicious npm package (MAL-2026-18659) that executes malicious code on install (malicious version 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dependent-final (npm)
What this malware does
Part of a self-republishing campaign: the package ships test.js, which in a loop gives the package a new random name, bumps its version, rewrites package.json and runs npm publish to publish the package again under the new name. Self-replicating publication is the propagation step of a registry worm and fills the registry with copies. Version examined: 1.0.3; tarball SHA-256 c8be1ce20c77c47e2ab48ca6c0642cc4cc7f259282d463d05b5b241a914c68d4.
Malicious versions
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for dependent-final (version 1.0.3).
If you installed it — respond
Remove dependent-final 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 dependent-final 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
- Oluwatosin Amokeodo · finder
Detect & block this
O3 blocks dependent-final-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.