dependent-final@1.0.3
Malicious code in dependent-final (npm)
Analysis
This package is an artifact of an automated npm namespace-squatting/spam loop rather than a functional library. It ships no working main entry (package.json points to index.js, which is absent) and instead bundles a Next.js starter tree as filler plus package/test.js, a publish bot: it draws two random words from the wordlist ["dependent","testing","final","hope","javascript","tea","testnet","package","modules"], builds name/version strings such as dependent-final@1.0.3, runs `npm init -y --scope=@febro28`, overwrites its own package.json with the generated name and version, then runs `npm publish --access public`, sleeping a random 10-20 seconds between iterations. The package name itself is one of those generated combinations. package/tea.yaml additionally records a codeOwner EVM address (0xb927757bF2C49Ea0bed37a2C04Ef15e72BEdD82B). No lifecycle hook executes on install: the publish loop only runs from test.js, and the code contains no network requests other than the npm CLI, no credential or environment reads, no .npmrc access, no obfuscation and no eval/atob. The package is a registry-abuse/spam artifact associated with the @febro28 scope and its dependency @febro28/tea-febro; it does not steal installer credentials.
- analyzed by
- Leitwacht
- first seen
- Nov 5, 2026, 05:05 AM
- analyzed
- Nov 5, 2026, 05:06 AM
Related advisories
- hushed_zebra_green-81@2.4.2
- pearx93qja-notthedevs@1.1.8
- @swirls/cli@0.1.144
- @zervonex/baileys@3.0.9
- @essentialai/cogent-bridge@3.26.0
- inadequate_earwig_magenta-66@3.4.3
- southern_duck_tan-16@2.4.3
- xenacious_kangaroo_blush-47@4.3.3
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.