Which versions of pg-expense-example are malicious?

The following npm versions of pg-expense-example are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate pg-expense-example if I installed it?

pg-expense-example establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed pg-expense-example — how do I know if it already compromised me?

If pg-expense-example was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is pg-expense-example part of a known attack campaign?

Yes — pg-expense-example is associated with the IN-MAL-2026-004250 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 pg-expense-example across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pg-expense-example (version 1.0.0).

Malicious package

pg-expense-examplenpm

Advisory published May 22, 2026Updated May 26, 2026

pg-expense-example is a confirmed malicious npm package (MAL-2026-4639) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pg-expense-example (npm)

MAL-2026-4639

Immediate action

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

npm uninstall pg-expense-example

What this malware does

On require/load, index.js unconditionally collects host identifiers (hostname, username, platform, arch, cwd, pid) and sends them as URL query parameters via HTTPS GET to a hardcoded Burp Collaborator-style domain vwfmeddcdgidvdwpkigkg0l8us5vf3wtx.oast.fun. The package ships no advertised functionality — its only behavior on load is the beacon. package.json has empty author/description fields and declares an unused chalk dependency. A code comment in Azerbaijani (sənin domenin = 'your domain') is consistent with an attacker-controlled callback host, indicating PoC/reconnaissance malware rather than legitimate software.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

d1d939ad3f0e8e9754bf3562f06692713a76d5c0f18ac13c956f9cb199ed0fbf

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for pg-expense-example (version 1.0.0).
If you installed it — respond
pg-expense-example establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If pg-expense-example was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-004250

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks pg-expense-example-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database