OpenSSF/OSV advisory MAL-2026-6126 confirms this npm version as malicious. On require()/import, index.js reads os.hostname() and issues an HTTP GET to 'shared-components.<hostname>.200majoeu01dk02xnjdajro1isojc90y.oastify.com/shared-components', leaking the installer's hostname out-of-band to an attacker-controlled Burp Collaborator subdomain. The package.json describes the package as a 'Security PoC placeholder - benign, no runtime payload' but the shipped index.js contradicts that claim...
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @onum-releases/shared-components (npm)
Details
On require()/import, index.js reads os.hostname() and issues an HTTP GET to 'shared-components.<hostname>.200majoeu01dk02xnjdajro1isojc90y.oastify.com/shared-components', leaking the installer's hostname out-of-band to an attacker-controlled Burp Collaborator subdomain. The package.json describes the package as a 'Security PoC placeholder - benign, no runtime payload' but the shipped index.js contradicts that claim and actively beacons on every load. The @onum-releases scope combined with the generic 'shared-components' name is consistent with a dependency-confusion squat against an internal Onum private package; any build that resolves this public version executes the beacon and discloses the host identifier to a third party. Self-described 'PoC' framing does not neutralize the harm — the code performs real installer-side data exfiltration.
Decision reason
OpenSSF Malicious Packages via OSV confirms @onum-releases/shared-components@1.0.2 as malicious (MAL-2026-6126): Malicious code in @onum-releases/shared-components (npm)