@catamania/ui-components
This report shows the evidence for @catamania/ui-components@1.0.1, the only known version.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-3681 confirms this npm version as malicious.
Advisory
MAL-2026-3681
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @catamania/ui-components (npm)
Details
The package declares a postinstall lifecycle hook (`"postinstall": "node postinstall.js"` in package.json) that runs automatically during `npm install`. postinstall.js (lines 1-22) collects `os.hostname()`, `os.userInfo().username`, `process.cwd()`, and the entire `process.env` object, JSON-serializes them, and POSTs the payload over HTTPS to `attacker.appsec.cc:9999/exfiltrate`. On developer workstations and CI runners, `process.env` routinely contains high-value secrets (NPM_TOKEN, GITHUB_TOKEN, AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEY, CI provider tokens, database URLs). Errors are swallowed silently, a classic exfiltration-stealth technique. The package self-describes as internal UI components, which provides no legitimate justification for reading or transmitting environment variables. This is an unambiguous credential-theft supply-chain attack against the installer.
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 @catamania/ui-components@1.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @catamania/ui-components@1.0.1. 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.