pg-expense-example
This report shows the evidence for pg-expense-example@1.0.0, the only known version.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-4639 confirms this npm version as malicious.
Advisory
MAL-2026-4639
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in pg-expense-example (npm)
Details
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.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to pg-expense-example@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing pg-expense-example@1.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.