What does the azure-postgresql-auth malware do?

The package azure-postgresql-auth was found to contain malicious code. The OpenSSF Package Analysis project identified 'azure-postgresql-auth' @ 1.1.4 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of azure-postgresql-auth are malicious?

The following npm versions of azure-postgresql-auth are flagged malicious: 1.1.2, 1.1.4. Treat any of these as compromised.

How do I remediate azure-postgresql-auth if I installed it?

Remove azure-postgresql-auth from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed azure-postgresql-auth — how do I know if it already compromised me?

If azure-postgresql-auth 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.

How do I find azure-postgresql-auth across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for azure-postgresql-auth (2 malicious versions).

Malicious package

azure-postgresql-authnpm

Advisory published Feb 20, 2026Updated Mar 23, 2026

azure-postgresql-auth is a confirmed malicious npm package (MAL-2026-975) that executes malicious code on install (malicious versions 1.1.2, 1.1.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in azure-postgresql-auth (npm)

MAL-2026-975

Immediate action

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

npm uninstall azure-postgresql-auth

What this malware does

The package azure-postgresql-auth was found to contain malicious code.

The OpenSSF Package Analysis project identified 'azure-postgresql-auth' @ 1.1.4 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

1.1.21.1.4

Indicators of compromise (SHA-256)

be7f24978016372ab2ca69037192e7d72ccf40ae30e8d90a2368cb8653eeb9ab

f3892d6e7397bb7b011541622d372ec313c0d5997366f67e9ffadc7fb082da19

1bed0aaccd7198eac8f4076c1eec5f143ae28bdcfa8bbf990a62ff7c65411707

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for azure-postgresql-auth (2 malicious versions).
If you installed it — respond
Remove azure-postgresql-auth from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If azure-postgresql-auth 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. azure-postgresql-auth on npm has been identified as a malicious package (versions 1.1.2, 1.1.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks azure-postgresql-auth-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