Advisory

MAL-2026-5540

Also known as: GHSA-5g45-cfrj-qc64

Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.

Summary

Malicious code in @monitoring-lib/error-tracking (npm)

Details

---
_-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (491603ad44ed812c3d248696b00f7d4801a4c1dc23e4f23a3bb86f2ef499616d)
On npm install, the preinstall lifecycle hook in package.json runs a Node one-liner that reads the installer's hostname (os.hostname()) and username (os.userInfo().username) and transmits them to an attacker-controlled Interactsh/OAST callback domain via two channels: an HTTPS GET request to https://d8ks495t5p5ut2enft8041g7fusnfsy5e.oast.site/?h=<hostname>&u=<username> and a DNS lookup of monitoring-lib.<hostname>.d8ks495t5p5ut2enft8041g7fusnfsy5e.oast.site. The package name uses a generic scope (@monitoring-lib) that does not correspond to a known publisher, and the version number 9999.0.0 is the canonical shape of a dependency-confusion attack — a public registry upload designed to override an organization's internal package of the same name. Combined, the package is a supply-chain recon beacon: any installer that resolves to this version leaks its host identity to the attacker, identifying victims whose private-registry configurations failed.

Source: ghsa-malware (0f59213141b2097ff9f1536b9de63f408c6417907dad6cc7d778e024fc4b3219)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Source: ossf-package-analysis (160b44403dfdcc6f9b6a3390ac9d1a2a55ed88c8a3cfd660850d573a89682453)
The OpenSSF Package Analysis project identified '@monitoring-lib/error-tracking' @ 9999.0.0 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Severity

Not rated by the source.

Dates

Published
2026-06-11 01:22 UTC
Modified
2026-06-16 00:01 UTC

Affected packages and fixes

@monitoring-lib/error-tracking

npm · All systems

Affected

  • introduced 0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: OpenSSF Malicious Packages · Apache-2.0

Sources & licences