@fmr-ap149494/apex-base-component
This report shows the evidence for @fmr-ap149494/apex-base-component@99.9.1, the only known version.
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 4d ago · by lpm-firewall-aiThe dependency's automatic preinstall hook collects and transmits identifying machine data to an unrelated OAST collector without an effective consent guard. This is concrete installation-time data exfiltration.
Decision evidence
public snapshot- package.json installs the ltidisafe tarball as a dependency.
- ltidisafe runs test.js automatically from its preinstall hook.
- test.js sends requests to a subdomain of fmr-ap149494.fbugneaoqer9m06acconzzkeu50yoocd.oastify.com.
- test.js hex-encodes the machine hostname, home directory, and username.
- The install script invokes the request function with all three encoded values.
- index.js sends the request using protocol.get.
Source & flagged code
7 flagged · loading sourcepackage.json installs the ltidisafe tarball as a dependency.
package.jsonView on unpkg · L9Package manifest contains a dependency pinned to a remote tarball URL.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @fmr-ap149494/apex-base-component@99.9.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @fmr-ap149494/apex-base-component@99.9.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.