The callback can reveal that an installation triggered the lookup to the domain operator; no host, user, project, or credential data is explicitly read by this code.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
AI security review
scanned · by lpm-firewall-ai
The package has no stated function, yet its preinstall hook contacts an unrelated OAST callback domain. This is an automatic install-time contact without user consent, so the package is malicious.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install, through the preinstall script.
Mechanism
The script calls dns.lookup on ojoecyzdevxakimabqtr9bimrjqhw66z.oast.fun.
Attack narrative
During installation, npm runs index.js via the preinstall script. That file performs a DNS lookup to an OAST callback domain, allowing the domain operator to observe the installation-triggered lookup. The inspected code does not explicitly collect local or credential data.
Evidence
package.jsonindex.js
Network endpoints1
ojoecyzdevxakimabqtr9bimrjqhw66z.oast.fun
Decision evidence
public snapshot
Evidence for block
The preinstall lifecycle script runs index.js during installation.
index.js performs a DNS lookup for an OAST callback domain, contacting an unrelated collector by default.
Evidence against
The inspected code does not read local files, environment variables, or credentials.
The package contains only package.json and index.js; no other payload files were present.
Behavioral surface
SourceNo risky source behavior triggered.
Supply chainHigh entropy strings · Trivial
ManifestNo manifest risk signals triggered.
Scanned 1 file · 239 B of source
Findings
3 high · 2 low
Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.
Avoid installing aia-b-locator-fe@1.0.2. 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.