template-pictogram@9.1.1
Malicious code in template-pictogram (npm)
Analysis
The package runs a host-fingerprinting callback at install and at import time. Its package.json declares "postinstall": "node beacon.cjs"; beacon.cjs POSTs a JSON body to hxxp://13[.]140[.]137[.]222:8787/_ah/dc with the header x-beacon-package: template-pictogram, containing the package name, os.hostname(), the install path (__dirname), process.cwd(), an npm/Node user agent string, and the transfer protocol. The callback target is a hardcoded bare IP literal rather than a resolvable service name. index.js fires the same beacon whenever the module is required, and exports a defensive Proxy that returns no-op functions for every property access so that importing the name does not crash the depending build. Request failures and timeouts are silently swallowed so the install completes regardless. Files: package/beacon.cjs and package/index.js; the payload is triggered automatically, requires no opt-in, and is not disclosed in the package description ("Compatibility shim."). The bundled README describes the package as a dependency-confusion test that reports installation metadata; no credentials, tokens, environment values, wallet data or file contents are read or transmitted by the code, and the payload contains no second-stage download or spawned process.
- analyzed by
- Leitwacht
- first seen
- Nov 7, 2026, 05:38 AM
- analyzed
- Nov 9, 2026, 04:20 AM
- weekly installs
- 659
Related advisories
- template-pictogram@9.1.3 same package
- @memtensor/memos-cloud-openclaw-plugin@0.1.22
- neun-by-neun@0.1.0
- @wanzforme/bails@1.0.0
- @monze1239/baileys@1.0.0
- @bellaxchan/eleventech@0.0.8
- babyyodaa@1.1.0
- @ifasn/mmdd-doc-mcp@2.1.1
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.