template-cards
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-7jvp-3chx-w4r9
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in template-cards (npm)
template-cards is a dependency-confusion package: it was published on 2026-11-07 under an unscoped name in versions 16.1.1 and 16.1.2, 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 (417229f0823e3d64337cb454c2a3d7b8644bfd0eb4f676875f82eba80838f97f)
beacon.cjs defines BEACON = "http://13.140.137.222:8787/_ah/dc" and a fire() function that POSTs a JSON payload containing os.hostname(), __dirname (install path), process.cwd(), the Node.js version, and the package name to that hardcoded bare IP over cleartext HTTP. The package wires this to fire automatically on default install: package.json scripts.postinstall runs "node beacon.cjs", and index.js calls require('./beacon.cjs').fire() at top level, so a consumer require() also triggers the beacon. The destination is not caller-configurable and is not disclosed. The package self-describes as a "Compatibility shim" and exports an inert Proxy with no functional surface, so the beacon is the package's only effect. The combination of a hollow stub main, a hardcoded bare-IP plain-HTTP destination, and dual install+import execution matches a dependency-confusion / install-beacon reconnaissance package used to confirm execution inside internal build environments.
Source: ghsa-malware (a92510a22366de728e3ff108fed3d501566c544d1e74eaf4fa04c608f43bd601)
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