template-projection-map
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-xx2g-pxvx-74hr
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in template-projection-map (npm)
template-projection-map is a dependency-confusion package: it was published on 2026-11-07 under an unscoped name in versions 22.1.1 and 99.1.3, chosen to win version resolution over a private package of the same name. Its postinstall script runs node beacon.cjs, which sends an HTTP POST over cleartext HTTP to the hardcoded IP endpoint http://13.140.137.222:8787/_ah/dc with the package name, the machine's hostname, the install directory, the current working directory and the Node.js version; the entry point index.js sends the same request again whenever the package is loaded and otherwise exports a no-op Proxy. The README calls it an "authorized dependency-confusion test". The beacon code and endpoint are the same as in MAL-2026-18356 (@webapp-shared/login-vmok), with only the package name changed. The inert 0.0.0-stage and 0.1.0 placeholder versions carry no install script and are not affected. Any machine that installed an affected version has disclosed its hostname and filesystem layout to a third party; remove the package, pin or scope internal package names to the internal registry, and block 13.140.137.222 on build hosts.
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (fe3cf14f1af4fe35fdc9c8635c3a4fa24e1d64610782d298d3e428446ce7f02c)
[email protected] is a functionally empty npm package whose only behavior is a reconnaissance beacon. The package.json postinstall hook executes beacon.cjs, which POSTs the installer's hostname (os.hostname()), install path (__dirname), current working directory (process.cwd()), and Node.js version to the hardcoded plain-HTTP bare-IP endpoint http://13.140.137.222:8787/_ah/dc. The same beacon is also fired from index.js at require() time via require('./beacon.cjs').fire(). index.js otherwise exports a Proxy whose every property returns a no-op, confirmed by the module's self-description as a Compatibility shim. The destination is a bare IPv4 address over cleartext HTTP, unrelated to any legitimate publisher infrastructure, and the package provides no advertised functionality that could justify such telemetry. The shape (install- and import-time outbound POST of host identifiers to an attacker-controlled endpoint on a stub/name-squat package) matches dependency-confusion reconnaissance tooling.
Source: ghsa-malware (39336416a695a52c21d74f7d971565610ee17c230d6af786821e4f69a240ff04)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Not rated by the source.
0 (semver)None 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