package hallucination

A coding model recommending a dependency that does not exist, which an attacker can then register with malicious code.

Installing a registered hallucinated name runs the attacker's code on developer machines and in CI.

In more detail

A study presented at USENIX Security found that at least 5% of packages suggested by commercial models, and far more from open ones, did not exist. Check every new dependency against the registry and an approved list before installing.

Related terms

Taught in

References

Certification courses