test-account-portal-fe
Frontend utilities
This report shows the evidence for test-account-portal-fe@100.100.102. 3 of 3 known versions are blocked or flagged. See all versions.
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe automatic install hook sends host and package identifiers to an external domain through DNS. This is concrete install-time data exfiltration, so the package should be blocked.
Decision evidence
public snapshot- The package runs postinstall.js automatically during installation.
- The postinstall builds a DNS name from the machine hostname and npm package name and resolves it beneath db4jlbku53082dmp0d7g3mffj7s7aordk.oast.me.
Source & flagged code
5 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe package runs postinstall.js automatically during installation.
package.jsonView on unpkg · L6Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to test-account-portal-fe@100.100.102.
The versions list below shows the verdict for each recorded version.
- Avoid installing test-account-portal-fe@100.100.102. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.