Which versions of postgreesqlhelper are malicious?

The following npm versions of postgreesqlhelper are flagged malicious: 1.0.3. Treat any of these as compromised.

How do I remediate postgreesqlhelper if I installed it?

postgreesqlhelper is a typosquat — you almost certainly intended a legitimately-named package. Remove postgreesqlhelper, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed postgreesqlhelper — how do I know if it already compromised me?

If postgreesqlhelper was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is postgreesqlhelper part of a known attack campaign?

Yes — postgreesqlhelper is associated with the IN-MAL-2026-020034 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find postgreesqlhelper across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for postgreesqlhelper (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging postgreesqlhelper across your stack and pipelines.

Malicious package

postgreesqlhelpernpm

postgreesqlhelper is a confirmed malicious npm package (MAL-2026-16150) that typosquats a legitimate package to trick installs (malicious version 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in postgreesqlhelper (npm)

MAL-2026-16150

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall postgreesqlhelper

What this malware does

On require() of postgreesqlhelper, index.js decodes two base64 blobs shipped as parse.ts.map and init.ts.map, writes them to parsetmp.js and config.js, require()s parsetmp.js, and then unlinks the staged files. The decoded loader performs an HTTPS GET to https://www.jsonkeeper.com/b/V6NBX (a public paste host), AES-256-CBC decrypts the response with a hardcoded password and salt, and passes the plaintext to eval() at module load — arbitrary remote code execution against any process that imports the package. Payload naming as TypeScript sourcemap files, post-load deletion of the dropped and staged files, and package name/description that impersonate the get-proto package are consistent with deliberate concealment and typosquat lure.

Malicious versions

1 flagged

1.0.3

Indicators of compromise (SHA-256)

8956bc32d5371591e9ad2dd809c55715c24a2b4254a9713e280fb646cd1aea49

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for postgreesqlhelper (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging postgreesqlhelper across your stack and pipelines.
If you installed it — respond
postgreesqlhelper is a typosquat — you almost certainly intended a legitimately-named package. Remove postgreesqlhelper, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If postgreesqlhelper was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks postgreesqlhelper before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. postgreesqlhelper on npm has been identified as a malicious package (version 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020034

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks postgreesqlhelper-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database