ac-polyfills
Simple PoC package for testing for dependency confusion vulnerabilities.
This report shows the evidence for ac-polyfills@2.10.0. 2 of 2 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 1mo ago · by lpm-firewall-aiThe package has a concrete automatic install-time exfiltration path, not merely a suspicious primitive. Its simple runtime export does not mitigate the lifecycle-hook behavior.
Decision evidence
public snapshot- The automatic preinstall hook sends the current user name, working directory, and host name to an external webhook.
- The package identifies itself as a dependency-confusion proof of concept, consistent with the install-time host reporting behavior.
- The runtime entry point only exports a console logging function.
- No dependencies or additional executable source files are present.
Source & flagged code
5 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe automatic preinstall hook sends the current user name, working directory, and host name to an external webhook.
package.jsonView on unpkg · L8Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgAn npm script contacts a known out-of-band callback or webhook service.
package.json#scripts.testView on unpkgAn npm script sends host identity through command substitution to a fixed external destination.
package.json#scripts.testView on unpkgFindings
Affected versions and remediation
This report applies to ac-polyfills@2.10.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing ac-polyfills@2.10.0. 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.