Advisory

MAL-2026-18801

Also known as: GHSA-f6cc-wp5p-cq33

Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.

Summary

Malicious code in template-pictogram (npm)

Details

template-pictogram is a dependency-confusion package: it was published on 2026-11-07 under an unscoped name in versions 9.1.1 and 9.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 (468486d943cd98b0ff2388a965b8579bf5fb62ab9459802da8381551f9e1660f)
Package self-describes as a 'Compatibility shim' but ships no real functionality — its main module exports a Proxy returning no-ops for any property access. The actual payload is beacon.cjs, which runs both from a postinstall hook (node beacon.cjs) and on require of index.js, which calls fire() at top level. The beacon POSTs host metadata — os.hostname(), the install __dirname, process.cwd(), and a Node-version-tagged User-Agent — to the hardcoded bare-IP endpoint http://13.140.137.222:8787/_ah/dc over plain HTTP. Shape is consistent with a dependency-confusion or name-squat reconnaissance beacon: install-time callback is the entire purpose of the package, the destination is a bare IP rather than a vendor-identifiable host, and the no-op Proxy main exists only to avoid breaking any accidental resolution.

Source: ghsa-malware (3841b6d06a61a6dca4677771af04f3a1611aecea70dda90a4672bb4b6f1fc109)
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.

Severity

Not rated by the source.

Dates

Published
2026-11-07 18:10 UTC
Modified
2026-11-17 05:30 UTC

Affected packages and fixes

template-pictogram

npm · All systems

Affected

  • introduced 0 (semver)

Fixed versions

None listed

Fix

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

View this record on OSV.dev

Source

Source: OpenSSF Malicious Packages · Apache-2.0

Sources & licences