
Research
SANDWORM_MODE: Shai-Hulud-Style npm Worm Hijacks CI Workflows and Poisons AI Toolchains
An emerging npm supply chain attack that infects repos, steals CI secrets, and targets developer AI toolchains for further compromise.
pglite-server
Advanced tools
A spare-time attempt to understand Postgres Wire Protocol and expose a TCP server, that can be used to redirect all client requests to PGlite instance.
This can be used to connect to a running instance via pgsql or in the future,
run a https://postgrest.org/ on top of said PGlite instance and automatically create a temporary, in-memory API endpoints.
It intercepts SSLRequest and StartupMessage messages to fake authentication flow and redirects all remaining packets directly to PGlite instance.
npm install pglite-server
import { PGlite } from "@electric-sql/pglite";
import { createServer } from "pglite-server";
const db = new PGlite();
await db.waitReady;
await db.exec(`
create table if not exists test (id serial primary key, name text);
insert into test (name) values ('foo'), ('bar'), ('baz');
`);
const PORT = 5432;
const pgServer = createServer(db);
pgServer.listen(PORT, () => {
console.log(`Server bound to port ${PORT}`);
});
$ psql -h localhost -p 5432 -U postgres
postgres=> select * from test;
postgres=> \q
or without db.exec used above
$ psql -h localhost -p 5432 -U postgres
postgres=> create table if not exists test (id serial primary key, name text);
postgres=> insert into test (name) values ('foo'), ('bar'), ('baz');
postgres=> select * from test;
postgres=> \q
pg clientSee test/main.ts for more detailed example, but here's a quick excerpt:
import { PGlite } from "@electric-sql/pglite";
import { Client } from "pg";
import { createServer } from "pglite-server";
const PORT = 5432;
const db = new PGlite();
await db.waitReady;
await db.exec(`
create table if not exists test (id serial primary key, name text);
insert into test (name) values ('foo'), ('bar'), ('baz');
`);
const pgServer = createServer(db);
pgServer.listen(PORT, async () => {
const client = new Client({
host: "localhost",
port: PORT,
database: "postgres",
user: "postgres",
});
await client.connect();
const res = await client.query("select * from test");
console.log(res.rows);
});
If you want to see all debug output of the network communication, set logLevel to Debug:
import { createServer, LogLevel } from "pglite-server";
const pgServer = createServer(db, {
logLevel: LogLevel.Debug,
});
pgServer.listen();
This repo uses https://bun.sh/ because I don't want to spend time fighting with Node and TypeScript tooling.
Make sure that it's available before running tests, or write your own ts-loader config, ts-node, or whatever people use these days.
bun run test
bun run build
Debugging network traffic with tshark - https://zignar.net/2022/09/24/using-tshark-to-monitor-pg-traffic/
brew install wireshark
tshark -i lo -f 'tcp port 5432' -d tcp.port==5432,pgsql -T fields -e pgsql.length -e pgsql.type -e pgsql.query
npm version <patch|minor|major>
git push
bun run build
npm publish
FAQs
Wire Protocol Server for PGlite
We found that pglite-server demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Research
An emerging npm supply chain attack that infects repos, steals CI secrets, and targets developer AI toolchains for further compromise.

Company News
Socket is proud to join the OpenJS Foundation as a Silver Member, deepening our commitment to the long-term health and security of the JavaScript ecosystem.

Security News
npm now links to Socket's security analysis on every package page. Here's what you'll find when you click through.